When CRAN archives an R package, it leaves the main repository but stays in the Archive area. Per CRAN policy, packages are not normally removed, but they may be archived, including at the maintainer's request. Projects that depend on an archived package can break on a fresh install.
What CRAN policy states
The repository policy says packages will not normally be removed from CRAN, but they may be archived, including at the maintainer's request. It also says that packages whose check gives an ERROR when a new R x.y.0 version is released will be archived, or in exceptional circumstances updated by the CRAN team, unless the maintainer has set a firm deadline for an update and keeps to it.
The policy also notes that package names are persistent, and that the CRAN team may orphan a package and allow another maintainer to take it over.
Why this matters for research code
A paper's code often depends on a handful of niche packages. Those are the ones most likely to have a single maintainer and the least likely to be updated quickly after an R release. If an analysis must be rerun years later, an archived dependency is a real failure mode, and an orphaned one raises a trust question about who maintains it now.
Steps to prepare
- List direct dependencies and mark which have a single maintainer or no recent release.
- Commit a lockfile so the exact versions are recorded.
- Keep a local copy of source tarballs for packages you cannot afford to lose, subject to their licenses.
- When a dependency is archived, check the Archive area for the last version and read why it was archived before deciding to install from there.
- If a package changes maintainers, read the new maintainer's history before updating. See what to do when a research tool maintainer disappears.
| Event | Risk to you | First action |
|---|---|---|
| Archived | Fresh installs fail | Pin and mirror last good version |
| Orphaned, new maintainer | Trust change | Review new maintainer and diff |
| Check ERROR on new R | May be archived soon | Watch for a fix or a deadline |
Try it yourself
Click through it at your own pace, or open it full screen. Look at how a project is watched over time, since a dependency can change status after you last checked.
Quick check
Does archived mean deleted?
No. Archived packages remain in CRAN's Archive area. They are no longer in the main repository, so default installs will not find them.
Can someone take over my package name?
CRAN policy says maintainers give CRAN the right to use the name on submission, so the team may orphan a package and let another maintainer take it over.
Safeguard can inventory dependencies and watch them continuously through its SBOM and dependency scanning. A free scan is available.
Sources
Last reviewed: 19 October 2026.
