native-buffer-browserify
Node.js Buffer API, for the browser
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used only in bin/test.js to run test suites — a standard dev/test pattern, not a runtime or install-time risk. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): cp.spawn in bin/test.js spawns 'npm run test-node' — a test runner invocation, not malicious code execution. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 3.2.2 | 3 / 10 | |
| 2.1.4 | 2 / 3 | |
| 2.1.3 | 2 / 3 | |
| 2.1.2 | 2 / 3 | |
| 2.1.1 | 2 / 3 | |
| 2.1.0 | 2 / 3 | |
| 2.0.17 | 2 / 3 | |
| 2.0.16 | 2 / 3 | |
| 2.0.15 | 2 / 3 | |
| 2.0.14 | 2 / 3 | |
| 2.0.13 | 2 / 2 | |
| 2.0.12 | 2 / 3 | |
| 2.0.10 | 2 / 3 | |
| 2.0.9 | 2 / 3 | |
| 2.0.8 | 2 / 3 | |
| 2.0.7 | 2 / 3 | |
| 2.0.5 | 2 / 3 | |
| 2.0.3 | 2 / 3 | |
| 2.0.2 | 2 / 3 | |
| 2.0.0 | 2 / 3 | |
| 1.2.4 | 2 / 3 | |
| 1.2.3 | 2 / 3 | |
| 1.2.2 | 2 / 3 | |
| 1.2.1 | 2 / 3 | |
| 1.2.0 | 2 / 3 | |
| 1.1.0 | 2 / 3 | |
| 1.0.3 | 1 / 3 | |
| 1.0.2 | 1 / 3 | |
| 1.0.1 | 1 / 3 | |
| 1.0.0 | 1 / 3 | |
| 0.5.0 | 1 / 3 | |
| 0.3.0 | 2 / 4 |
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.