adm-zip
Javascript implementation of zip for nodejs with support for electron original-fs. Allows user to create or extract zip files both in memory or to/from disk
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:another-d-mention.ro | AI (email-domain): This email domain has been associated with adm-zip since its initial publication 5173 days ago. The lapsed domain is a latent risk but not evidence of a takeover; the package is well-established with consistent authorship. | ai | |
| provenance | no-provenance | AI (provenance): adm-zip is a long-established package; lack of provenance attestation is consistent with its entire publishing history and not a meaningful risk signal here. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.5.17 | 0 / 5 | |
| 0.5.16 | 0 / 5 | |
| 0.5.15 | 0 / 5 | |
| 0.5.14 | 0 / 4 | |
| 0.5.13 | 0 / 4 | |
| 0.5.12 | 0 / 4 | |
| 0.5.11 | 0 / 4 | |
| 0.5.10 | 0 / 4 | |
| 0.5.9 | 0 / 4 | |
| 0.5.8 | 0 / 4 | |
| 0.5.7 | 0 / 4 | |
| 0.5.6 | 0 / 4 | |
| 0.5.5 | 0 / 3 | |
| 0.5.4 | 0 / 3 | |
| 0.5.3 | 0 / 3 | |
| 0.5.2 | 0 / 3 | |
| 0.5.1 | 0 / 3 | |
| 0.5.0 | 0 / 3 | |
| 0.4.16 | 0 / 3 | |
| 0.4.14 | 0 / 3 | |
| 0.4.13 | 0 / 3 | |
| 0.4.11 | 0 / 0 |
v0.5.16
2 findingsMaintainer email '[email protected]' uses domain 'another-d-mention.ro' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
2 findingsMaintainer email '[email protected]' uses domain 'another-d-mention.ro' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
2 findingsMaintainer email '[email protected]' uses domain 'another-d-mention.ro' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
2 findingsMaintainer email '[email protected]' uses domain 'another-d-mention.ro' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
2 findingsMaintainer email '[email protected]' uses domain 'another-d-mention.ro' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
2 findingsMaintainer email '[email protected]' uses domain 'another-d-mention.ro' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
2 findingsMaintainer email '[email protected]' uses domain 'another-d-mention.ro' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
2 findingsMaintainer email '[email protected]' uses domain 'another-d-mention.ro' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.