@ast-grep/napi
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): @ast-grep/napi is a scoped package for the ast-grep project; 'napi' refers to Node.js native addon interface, not a typosquat of 'hapi'. False positive for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used only to run 'ldd --version' to detect musl libc for native binary selection — standard napi-rs pattern, not malicious. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): execSync('ldd --version') is a hardcoded, benign musl detection call used by napi-rs native bindings to select the correct prebuilt binary. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require via NAPI_RS_NATIVE_LIBRARY_PATH env var is a documented napi-rs override mechanism, not an arbitrary code execution risk. | ai |
Versions (showing 84 of 84)
| Version | Deps | Published |
|---|---|---|
| 0.43.0 | 0 / 10 | |
| 0.42.3 | 0 / 10 | |
| 0.42.2 | 0 / 10 | |
| 0.42.1 | 0 / 10 | |
| 0.42.0 | 0 / 10 | |
| 0.41.1 | 0 / 10 | |
| 0.41.0 | 0 / 10 | |
| 0.40.5 | 0 / 10 | |
| 0.40.4 | 0 / 10 | |
| 0.40.3 | 0 / 10 | |
| 0.40.2 | 0 / 10 | |
| 0.40.1 | 0 / 10 | |
| 0.40.0 | 0 / 10 | |
| 0.39.9 | 0 / 10 | |
| 0.39.7 | 0 / 10 | |
| 0.39.6 | 0 / 10 | |
| 0.39.5 | 0 / 10 | |
| 0.39.4 | 0 / 10 | |
| 0.39.3 | 0 / 10 | |
| 0.39.2 | 0 / 10 | |
| 0.39.1 | 0 / 10 | |
| 0.38.7 | 0 / 9 | |
| 0.38.6 | 0 / 9 | |
| 0.38.5 | 0 / 9 | |
| 0.38.4 | 0 / 9 | |
| 0.38.3 | 0 / 9 | |
| 0.38.2 | 0 / 9 | |
| 0.38.1 | 0 / 9 | |
| 0.38.0 | 0 / 9 | |
| 0.37.0 | 0 / 9 | |
| 0.36.3 | 0 / 9 | |
| 0.36.2 | 0 / 9 | |
| 0.36.1 | 0 / 9 | |
| 0.36.0 | 0 / 9 | |
| 0.35.0 | 0 / 9 | |
| 0.34.4 | 0 / 9 | |
| 0.34.3 | 0 / 9 | |
| 0.34.2 | 0 / 9 | |
| 0.34.1 | 0 / 9 | |
| 0.33.1 | 0 / 9 | |
| 0.33.0 | 0 / 9 | |
| 0.32.3 | 0 / 9 | |
| 0.32.2 | 0 / 9 | |
| 0.32.1 | 0 / 9 | |
| 0.32.0 | 0 / 9 | |
| 0.31.1 | 0 / 5 | |
| 0.31.0 | 0 / 5 | |
| 0.30.1 | 0 / 5 | |
| 0.30.0 | 0 / 5 | |
| 0.29.0 | 0 / 5 | |
| 0.28.1 | 0 / 5 | |
| 0.28.0 | 0 / 5 | |
| 0.27.3 | 0 / 5 | |
| 0.27.2 | 0 / 5 | |
| 0.27.1 | 0 / 5 | |
| 0.27.0 | 0 / 5 | |
| 0.26.3 | 0 / 5 | |
| 0.26.2 | 0 / 5 | |
| 0.26.1 | 0 / 5 | |
| 0.26.0 | 0 / 5 | |
| 0.25.7 | 0 / 5 | |
| 0.25.6 | 0 / 5 | |
| 0.25.5 | 0 / 5 | |
| 0.25.4 | 0 / 5 | |
| 0.25.3 | 0 / 5 | |
| 0.25.2 | 0 / 5 | |
| 0.25.1 | 0 / 5 | |
| 0.25.0 | 0 / 5 | |
| 0.24.1 | 0 / 5 | |
| 0.24.0 | 0 / 5 | |
| 0.23.1 | 0 / 5 | |
| 0.23.0 | 0 / 5 | |
| 0.22.6 | 0 / 5 | |
| 0.22.5 | 0 / 5 | |
| 0.22.4 | 0 / 5 | |
| 0.22.3 | 0 / 5 | |
| 0.22.2 | 0 / 5 | |
| 0.22.1 | 0 / 5 | |
| 0.22.0 | 0 / 5 | |
| 0.21.4 | 0 / 5 | |
| 0.21.3 | 0 / 5 | |
| 0.21.2 | 0 / 5 | |
| 0.21.1 | 0 / 5 | |
| 0.21.0 | 0 / 5 |
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.1
2 findingsPackage name '@ast-grep/napi' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.