@ast-grep/napi No license 29 versions

@ast-grep/napi

npm Repository Homepage

29

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

herringtondarkholme

Keywords

astpatterncodemodsearchrewrite

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	2026/04/24
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	2026/04/24
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	2026/04/24
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	2026/04/24

Versions (showing 29 of 29)

Version	Deps	Published
0.43.0	0 / 10	2026-05-25
0.42.3	0 / 10	2026-05-19
0.42.2	0 / 10	2026-05-10
0.42.1	0 / 10	2026-04-04
0.42.0	0 / 10	2026-03-16
0.41.1	0 / 10	2026-03-10
0.41.0	0 / 10	2026-02-22
0.40.5	0 / 10	2026-01-10
0.40.4	0 / 10	2026-01-05
0.40.3	0 / 10	2025-12-15
0.40.2	0 / 10	2025-12-15
0.40.1	0 / 10	2025-12-11
0.40.0	0 / 10	2025-11-16
0.39.9	0 / 10	2025-11-07
0.39.7	0 / 10	2025-10-27
0.39.6	0 / 10	2025-10-05
0.39.5	0 / 10	2025-09-08
0.39.4	0 / 10	2025-08-17
0.39.3	0 / 10	2025-08-05
0.39.2	0 / 10	2025-07-27
0.39.1	0 / 10	2025-07-21
0.38.7	0 / 9	2025-07-10
0.38.6	0 / 9	2025-06-24
0.38.5	0 / 9	2025-06-08
0.38.4	0 / 9	2025-06-02
0.38.3	0 / 9	2025-05-28
0.38.2	0 / 9	2025-05-18
0.38.1	0 / 9	2025-05-11
0.38.0	0 / 9	2025-05-10

v0.43.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.42.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.42.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.42.1

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@ast-grep/napi' is 1 edit(s) away from popular package 'hapi'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.42.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.41.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.41.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.40.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.40.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.40.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.40.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.40.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.40.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.39.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.39.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.39.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.39.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.39.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.39.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.39.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.39.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.38.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.38.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.38.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.38.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.38.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.38.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.38.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.38.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.