extract-base-iterator
Base iterator for extract iterators like tar-iterator and zip-iterator
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:rimraf2 | AI (dependencies): rimraf2 is a utility from the same publisher ecosystem; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package; lack of provenance is consistent across its version history and not a risk signal here. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 3.4.5 | 9 / 11 | |
| 3.4.4 | 9 / 9 | |
| 3.4.3 | 9 / 9 | |
| 3.4.2 | 9 / 9 | |
| 3.4.1 | 9 / 9 | |
| 3.4.0 | 9 / 9 | |
| 3.3.5 | 9 / 9 | |
| 3.3.4 | 9 / 9 | |
| 3.3.3 | 9 / 9 | |
| 3.3.2 | 9 / 9 | |
| 3.3.1 | 9 / 9 | |
| 3.3.0 | 9 / 9 | |
| 3.2.2 | 11 / 9 | |
| 3.2.1 | 11 / 9 | |
| 3.2.0 | 11 / 9 | |
| 3.1.0 | 11 / 9 | |
| 3.0.2 | 11 / 9 | |
| 3.0.1 | 11 / 9 | |
| 3.0.0 | 11 / 9 | |
| 2.7.0 | 11 / 9 | |
| 2.6.1 | 11 / 9 | |
| 2.6.0 | 10 / 9 | |
| 2.5.0 | 10 / 10 | |
| 2.4.14 | 10 / 10 | |
| 2.4.13 | 10 / 10 | |
| 2.4.12 | 10 / 10 | |
| 2.4.11 | 10 / 10 | |
| 2.4.10 | 10 / 10 | |
| 2.4.8 | 10 / 10 | |
| 2.4.7 | 10 / 10 | |
| 2.4.6 | 10 / 10 | |
| 2.4.5 | 10 / 10 | |
| 2.4.4 | 10 / 10 | |
| 2.4.3 | 11 / 10 | |
| 2.4.2 | 11 / 10 | |
| 2.4.1 | 11 / 10 | |
| 2.4.0 | 11 / 10 | |
| 2.3.3 | 10 / 7 | |
| 2.3.2 | 10 / 7 | |
| 2.3.1 | 9 / 7 | |
| 2.3.0 | 9 / 7 |
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.