browser-pack
pack node-style source files from a json stream into a browser bundle
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): goto-bus-stop is a well-established browserify ecosystem maintainer with strong track record; the transition from zertosh is a documented legitimate handoff. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): The added maintainers are well-known Node.js/browserify ecosystem contributors reflecting the project's collaborative team structure. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): safe-buffer is a widely-trusted feross package for cross-version Buffer compatibility; its addition is a standard, benign practice. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 6.1.0 | 6 / 5 | |
| 6.0.4 | 6 / 5 | |
| 6.0.3 | 6 / 5 | |
| 6.0.2 | 5 / 5 | |
| 6.0.1 | 5 / 5 | |
| 6.0.0 | 5 / 5 | |
| 5.0.1 | 5 / 5 | |
| 5.0.0 | 6 / 4 | |
| 4.0.4 | 6 / 4 | |
| 4.0.3 | 6 / 4 | |
| 4.0.2 | 6 / 4 | |
| 4.0.1 | 6 / 4 | |
| 4.0.0 | 6 / 4 | |
| 3.2.0 | 6 / 5 | |
| 3.1.1 | 5 / 5 | |
| 3.1.0 | 5 / 5 | |
| 3.0.0 | 5 / 5 | |
| 2.0.1 | 3 / 5 | |
| 2.0.0 | 3 / 5 | |
| 1.1.0 | 3 / 5 | |
| 0.11.1 | 3 / 5 | |
| 0.11.0 | 3 / 5 | |
| 0.10.2 | 3 / 5 | |
| 0.10.1 | 3 / 5 | |
| 0.10.0 | 3 / 5 | |
| 0.9.4 | 3 / 5 | |
| 0.9.3 | 4 / 5 | |
| 0.9.2 | 4 / 5 | |
| 0.9.1 | 5 / 4 | |
| 0.9.0 | 5 / 4 | |
| 0.8.1 | 5 / 4 | |
| 0.8.0 | 5 / 4 | |
| 0.7.1 | 5 / 4 | |
| 0.7.0 | 5 / 4 | |
| 0.6.0 | 5 / 4 | |
| 0.5.0 | 5 / 4 | |
| 0.4.1 | 5 / 2 | |
| 0.4.0 | 5 / 2 | |
| 0.3.0 | 4 / 2 | |
| 0.2.1 | 3 / 2 | |
| 0.2.0 | 3 / 2 | |
| 0.1.2 | 3 / 2 | |
| 0.1.1 | 3 / 2 | |
| 0.0.0 | 3 / 2 |
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
2 findingsThis version was published by a different npm account than previous versions on 2018-01-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.