@chainsafe/zapi
A tool for managing and publishing Zig NAPI packages.
Supply chain provenance
Status for the latest visible version.
Maintainers
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): Used solely to detect musl libc via ldd --version for native binary selection; stable pattern for this package. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): execSync('ldd --version') is a fixed, safe command for musl detection; not user-controlled input. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @chainsafe package for Zig NAPI tooling; no relation to the hapi web framework. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads a local .node binary by path — standard NAPI native binding pattern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 0 / 5 | |
| 2.1.0 | 0 / 5 | |
| 2.0.0 | 0 / 5 | |
| 1.0.1 | 0 / 5 | |
| 0.1.1 | 0 / 2 |
v2.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
2 findingsPackage name '@chainsafe/zapi' is 1 edit(s) away from popular package 'hapi'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.