@vekexasia/bigint-buffer2
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node files are standard NAPI-RS artifacts for multiple platforms; package.json napi config and @napi-rs/cli devDep confirm legitimate native binding pattern. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used only for 'which ldd' to detect musl libc for native binary selection — standard pattern in NAPI-RS packages, publicly visible in repo. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): execSync('which ldd') is a benign musl detection pattern used in NAPI-RS native binding loaders; not arbitrary code execution. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 0 / 4 | |
| 1.1.0 | 0 / 4 | |
| 1.0.5 | 0 / 4 | |
| 1.0.4 | 0 / 4 | |
| 1.0.3 | 0 / 4 | |
| 1.0.2 | 0 / 4 | |
| 1.0.1 | 0 / 4 | |
| 1.0.0 | 0 / 4 |
v1.1.1
2 findingsPackage contains compiled binaries that could be backdoors: • index.darwin-arm64.node • index.darwin-x64.node • index.linux-arm64-gnu.node • index.linux-x64-gnu.node • index.win32-x64-msvc.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.