Archiving
Overview
JFrog Smart Archiving moves artifacts that are no longer in active use into a retained archive.
Why
- Obsolete releases, end-of-life artifacts, and orphaned dependencies build up and often cannot be deleted
- CI/CD slows down, and current artifacts are harder to find
- Bloated repositories slow releases and can raise failure rates
- Unmanaged artifacts expand the attack surface and the chance of a failed audit
- Storing and transferring inactive data is an ongoing cost
How
- Define policies for which packages to archive and when. Policies are scoped per project
- Dry-run a policy before any data moves
- Archiving runs automatically and keeps metadata, security attestations, and compliance data
- Reports show what would be archived and what was archived. Evidence stays available for restore
- The same policies work with federated repositories
Architecture
The following is a schematic high-level architecture of this topology.
