zip-stream
a streaming zip archive generator.
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): Transition from maintainer to GitHub Actions CI/CD with SLSA provenance; legitimate automation migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature, stable package; infrequent publishes are normal for its lifecycle. | ai | |
| phantom-deps | phantom-dep:readable-stream | AI (phantom-deps): readable-stream is a core streams polyfill; used transitively or via require in Node stream internals. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 7.0.5 | 3 / 8 | |
| 7.0.4 | 3 / 8 | |
| 7.0.2 | 3 / 8 | |
| 7.0.1 | 3 / 8 | |
| 7.0.0 | 3 / 8 | |
| 6.0.1 | 3 / 7 | |
| 6.0.0 | 3 / 7 | |
| 5.0.2 | 3 / 7 | |
| 5.0.1 | 3 / 7 | |
| 5.0.0 | 3 / 7 | |
| 4.1.1 | 3 / 7 | |
| 4.1.0 | 3 / 7 | |
| 4.0.4 | 3 / 7 | |
| 4.0.3 | 3 / 7 | |
| 4.0.2 | 3 / 7 | |
| 4.0.1 | 3 / 7 | |
| 4.0.0 | 3 / 7 | |
| 3.0.1 | 3 / 7 | |
| 3.0.0 | 3 / 7 | |
| 2.1.3 | 3 / 7 | |
| 2.1.2 | 3 / 7 | |
| 2.1.1 | 3 / 7 | |
| 2.1.0 | 3 / 7 | |
| 2.0.1 | 3 / 7 | |
| 2.0.0 | 3 / 7 | |
| 1.2.0 | 4 / 7 | |
| 1.1.1 | 4 / 7 | |
| 1.1.0 | 4 / 6 | |
| 1.0.0 | 4 / 6 | |
| 0.8.0 | 4 / 4 | |
| 0.7.0 | 3 / 4 | |
| 0.6.0 | 3 / 4 | |
| 0.5.2 | 3 / 4 | |
| 0.5.1 | 3 / 4 | |
| 0.5.0 | 3 / 4 | |
| 0.4.1 | 3 / 4 | |
| 0.4.0 | 3 / 4 | |
| 0.3.7 | 6 / 4 | |
| 0.3.6 | 6 / 4 | |
| 0.3.5 | 6 / 4 | |
| 0.3.4 | 6 / 4 | |
| 0.3.3 | 5 / 4 | |
| 0.3.2 | 5 / 4 | |
| 0.3.1 | 4 / 4 | |
| 0.3.0 | 4 / 4 | |
| 0.2.3 | 3 / 4 | |
| 0.2.2 | 3 / 4 | |
| 0.2.1 | 2 / 4 | |
| 0.2.0 | 2 / 4 | |
| 0.1.4 | 2 / 4 | |
| 0.1.3 | 2 / 4 |
v7.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.4
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.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.