browserify
browser-side require() the node way
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): Publisher change from goto-bus-stop to yoshuawuyts occurred in 2018; yoshuawuyts has a strong track record and this is a documented legitimate maintainer transition for the browserify project. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Browserify legitimately uses child_process to spawn transform subprocesses — core bundler functionality, not malicious. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Browserify reads process.env to pass environment variables to transforms, which is standard and documented bundler behavior. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is fundamental to how browserify loads user-specified plugins; this is expected and intentional design. | ai |
Versions (showing 100 of 485)
| Version | Deps | Published |
|---|---|---|
| 17.0.1 | 48 / 13 | |
| 17.0.0 | 48 / 13 | |
| 16.5.2 | 48 / 13 | |
| 16.5.1 | 48 / 13 | |
| 16.5.0 | 48 / 13 | |
| 16.4.0 | 48 / 13 | |
| 16.3.0 | 48 / 13 | |
| 16.2.3 | 48 / 13 | |
| 16.2.2 | 48 / 13 | |
| 16.2.1 | 48 / 13 | |
| 16.2.0 | 48 / 12 | |
| 16.1.1 | 48 / 12 | |
| 16.1.0 | 48 / 12 | |
| 16.0.0 | 48 / 12 | |
| 15.2.0 | 48 / 12 | |
| 15.1.0 | 47 / 11 | |
| 15.0.0 | 47 / 9 | |
| 14.5.0 | 47 / 10 | |
| 14.4.0 | 47 / 10 | |
| 14.3.0 | 47 / 10 | |
| 14.2.0 | 47 / 10 | |
| 14.1.0 | 47 / 10 | |
| 14.0.0 | 47 / 10 | |
| 13.3.0 | 47 / 10 | |
| 13.2.0 | 47 / 10 | |
| 13.1.1 | 47 / 10 | |
| 13.1.0 | 46 / 10 | |
| 13.0.1 | 46 / 10 | |
| 13.0.0 | 47 / 10 | |
| 12.0.2 | 47 / 10 | |
| 12.0.1 | 47 / 10 | |
| 12.0.0 | 47 / 10 | |
| 11.2.0 | 49 / 10 | |
| 11.1.0 | 49 / 10 | |
| 11.0.1 | 49 / 10 | |
| 11.0.0 | 49 / 10 | |
| 10.2.6 | 49 / 10 | |
| 10.2.5 | 49 / 10 | |
| 10.2.4 | 49 / 10 | |
| 10.2.3 | 50 / 10 | |
| 10.2.1 | 50 / 10 | |
| 10.2.0 | 51 / 10 | |
| 10.1.3 | 51 / 10 | |
| 10.1.2 | 51 / 10 | |
| 10.1.1 | 51 / 10 | |
| 10.1.0 | 51 / 10 | |
| 10.0.0 | 51 / 10 | |
| 9.0.8 | 50 / 10 | |
| 9.0.7 | 50 / 10 | |
| 9.0.6 | 50 / 10 | |
| 9.0.5 | 50 / 10 | |
| 9.0.4 | 49 / 9 | |
| 9.0.3 | 49 / 10 | |
| 9.0.2 | 49 / 10 | |
| 9.0.1 | 49 / 10 | |
| 9.0.0 | 49 / 10 | |
| 8.1.3 | 49 / 11 | |
| 8.1.2 | 49 / 11 | |
| 8.1.1 | 49 / 11 | |
| 8.1.0 | 49 / 11 | |
| 8.0.3 | 49 / 11 | |
| 8.0.2 | 49 / 11 | |
| 8.0.1 | 49 / 11 | |
| 8.0.0 | 49 / 11 | |
| 7.1.0 | 49 / 11 | |
| 7.0.3 | 49 / 11 | |
| 7.0.2 | 49 / 11 | |
| 7.0.1 | 49 / 11 | |
| 7.0.0 | 49 / 11 | |
| 6.3.4 | 49 / 11 | |
| 6.3.3 | 49 / 11 | |
| 6.3.2 | 49 / 11 | |
| 6.3.1 | 49 / 11 | |
| 6.3.0 | 49 / 11 | |
| 6.2.0 | 49 / 11 | |
| 6.1.2 | 49 / 11 | |
| 6.1.1 | 49 / 10 | |
| 6.1.0 | 49 / 10 | |
| 6.0.3 | 49 / 10 | |
| 6.0.2 | 49 / 10 | |
| 6.0.1 | 49 / 10 | |
| 6.0.0 | 49 / 10 | |
| 5.13.1 | 49 / 10 | |
| 5.13.0 | 49 / 10 | |
| 5.12.2 | 49 / 10 | |
| 5.12.1 | 50 / 10 | |
| 5.12.0 | 50 / 10 | |
| 5.11.2 | 50 / 10 | |
| 5.11.1 | 50 / 10 | |
| 5.11.0 | 50 / 10 | |
| 5.10.1 | 50 / 10 | |
| 5.10.0 | 50 / 10 | |
| 5.9.3 | 50 / 10 | |
| 5.9.2 | 50 / 10 | |
| 5.9.1 | 50 / 10 | |
| 5.9.0 | 50 / 10 | |
| 5.8.0 | 50 / 10 | |
| 5.7.0 | 50 / 10 | |
| 5.6.1 | 50 / 10 | |
| 5.6.0 | 50 / 10 |
v17.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.5.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-30. This could indicate a legitimate maintainer transition or an account compromise.
v16.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-08-08. This could indicate a legitimate maintainer transition or an account compromise.
v16.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-04-11. This could indicate a legitimate maintainer transition or an account compromise.
v16.1.1
2 findingsThis version was published by a different npm account than previous versions on 2018-03-06. 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.
v16.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.