archiver
a streaming interface for archive generation
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Moved to GitHub Actions CI/CD publishing with SLSA provenance; legitimate transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature package with infrequent major releases; 799-day gap is normal for stable software. | ai | |
| provenance | no-provenance | AI (provenance): archiver is a 4943-day-old package predating Sigstore provenance on npm; absence of attestation is expected and not a risk signal for this package. | ai | |
| dependencies | unvetted-dep:zip-stream | AI (dependencies): zip-stream is a first-party sibling package from the archiverjs org, maintained by the same author (ctalkington). It is a core, expected dependency of archiver. | ai | |
| dependencies | unvetted-dep:archiver-utils | AI (dependencies): archiver-utils is a first-party sibling package from the archiverjs org, maintained by the same author (ctalkington). It is a core, expected dependency of archiver. | ai |
Versions (showing 51 of 80)
| Version | Deps | Published |
|---|---|---|
| 8.0.0 | 9 / 10 | |
| 7.0.1 | 7 / 9 | |
| 7.0.0 | 7 / 9 | |
| 6.0.2 | 7 / 9 | |
| 6.0.1 | 7 / 9 | |
| 6.0.0 | 7 / 9 | |
| 5.3.2 | 7 / 9 | |
| 5.3.1 | 7 / 9 | |
| 5.3.0 | 7 / 9 | |
| 5.2.0 | 7 / 9 | |
| 5.1.0 | 7 / 9 | |
| 5.0.2 | 7 / 9 | |
| 5.0.1 | 7 / 9 | |
| 5.0.0 | 7 / 9 | |
| 4.0.2 | 7 / 9 | |
| 4.0.1 | 7 / 9 | |
| 4.0.0 | 7 / 9 | |
| 3.1.1 | 7 / 9 | |
| 3.1.0 | 7 / 9 | |
| 3.0.3 | 7 / 9 | |
| 3.0.1 | 7 / 9 | |
| 3.0.0 | 7 / 9 | |
| 2.1.1 | 8 / 9 | |
| 2.1.0 | 8 / 9 | |
| 2.0.3 | 9 / 9 | |
| 2.0.2 | 9 / 9 | |
| 2.0.1 | 9 / 9 | |
| 2.0.0 | 9 / 9 | |
| 1.3.0 | 9 / 9 | |
| 1.2.0 | 8 / 9 | |
| 1.1.0 | 8 / 9 | |
| 1.0.1 | 8 / 9 | |
| 1.0.0 | 8 / 9 | |
| 0.21.0 | 8 / 9 | |
| 0.20.0 | 8 / 7 | |
| 0.19.0 | 8 / 7 | |
| 0.18.0 | 8 / 7 | |
| 0.17.0 | 8 / 7 | |
| 0.16.0 | 8 / 7 | |
| 0.15.1 | 8 / 7 | |
| 0.15.0 | 8 / 7 | |
| 0.14.4 | 8 / 7 | |
| 0.14.3 | 8 / 7 | |
| 0.14.2 | 8 / 7 | |
| 0.14.1 | 8 / 7 | |
| 0.14.0 | 8 / 7 | |
| 0.13.1 | 8 / 7 | |
| 0.13.0 | 8 / 5 | |
| 0.12.0 | 8 / 5 | |
| 0.11.0 | 8 / 5 | |
| 0.10.1 | 7 / 5 |
v8.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-08. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.