@rspack/binding
Node binding for rspack
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): rspack migrated to GitHub Actions CI publishing with SLSA provenance attestation. This is a legitimate, security-improving transition for this established package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established rspack native binding package; spam signals are false positives — hardfist is a known rspack maintainer, short README and no keywords are typical for platform binding packages. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): execSync('ldd --version') is standard napi-rs pattern to detect musl libc for selecting the correct prebuilt binary. Benign and stable for this package. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): execSync('ldd --version') is standard napi-rs musl detection pattern. Benign and stable for this native binding package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): require(process.env.NAPI_RS_NATIVE_LIBRARY_PATH) is a documented napi-rs override mechanism for the native library path. Benign and stable for this package. | ai |
Versions (showing 100 of 207)
| Version | Deps | Published |
|---|---|---|
| 0.7.1 | 0 / 1 | |
| 0.7.0 | 9 / 1 | |
| 0.6.5 | 9 / 1 | |
| 0.6.4 | 9 / 1 | |
| 0.6.3 | 9 / 1 | |
| 0.6.2 | 9 / 1 | |
| 0.6.1 | 9 / 1 | |
| 0.6.0 | 9 / 1 | |
| 0.5.9 | 9 / 1 | |
| 0.5.8 | 9 / 1 | |
| 0.5.7 | 9 / 1 | |
| 0.5.6 | 9 / 1 | |
| 0.5.5 | 9 / 1 | |
| 0.5.4 | 9 / 1 | |
| 0.5.3 | 9 / 1 | |
| 0.5.2 | 9 / 1 | |
| 0.5.1 | 9 / 1 | |
| 0.5.0 | 9 / 1 | |
| 0.4.5 | 9 / 1 | |
| 0.4.4 | 9 / 1 | |
| 0.4.3 | 9 / 1 | |
| 0.4.2 | 9 / 1 | |
| 0.4.1 | 9 / 1 | |
| 0.4.0 | 9 / 1 | |
| 0.3.14 | 9 / 1 | |
| 0.3.13 | 9 / 1 | |
| 0.3.12 | 9 / 1 | |
| 0.3.11 | 9 / 1 | |
| 0.3.10 | 9 / 1 | |
| 0.3.9 | 5 / 1 | |
| 0.3.8 | 9 / 1 | |
| 0.3.7 | 9 / 1 | |
| 0.3.6 | 9 / 1 | |
| 0.3.5 | 9 / 1 | |
| 0.3.4 | 9 / 1 | |
| 0.3.3 | 9 / 1 | |
| 0.3.2 | 9 / 1 | |
| 0.3.1 | 9 / 1 | |
| 0.3.0 | 9 / 1 | |
| 0.2.12 | 9 / 1 | |
| 0.2.11 | 9 / 1 | |
| 0.2.10 | 9 / 1 | |
| 0.2.9 | 9 / 1 | |
| 0.2.8 | 9 / 1 | |
| 0.2.7 | 9 / 1 | |
| 0.2.6 | 9 / 1 | |
| 0.2.5 | 9 / 1 | |
| 0.2.4 | 9 / 1 | |
| 0.2.3 | 9 / 1 | |
| 0.2.2 | 9 / 1 | |
| 0.2.1 | 9 / 1 | |
| 0.2.0 | 9 / 1 | |
| 0.1.12 | 9 / 4 | |
| 0.1.11 | 9 / 4 | |
| 0.1.10 | 9 / 4 | |
| 0.1.9 | 9 / 4 | |
| 0.1.8 | 9 / 4 | |
| 0.1.7 | 9 / 4 | |
| 0.1.6 | 9 / 4 | |
| 0.1.5 | 9 / 4 | |
| 0.1.4 | 9 / 4 | |
| 0.1.3 | 9 / 4 | |
| 0.1.2 | 9 / 4 | |
| 0.1.1 | 9 / 3 | |
| 0.1.0 | 9 / 3 | |
| 0.0.26 | 9 / 3 | |
| 0.0.25 | 9 / 3 | |
| 0.0.24 | 4 / 3 | |
| 0.0.23 | 4 / 3 | |
| 0.0.22 | 4 / 3 | |
| 0.0.21 | 3 / 3 | |
| 0.0.20 | 3 / 3 | |
| 0.0.19 | 3 / 3 | |
| 0.0.18 | 3 / 3 | |
| 0.0.17 | 3 / 3 | |
| 0.0.16 | 3 / 3 | |
| 0.0.15 | 3 / 3 | |
| 0.0.14 | 3 / 3 | |
| 0.0.13 | 3 / 3 | |
| 0.0.12 | 0 / 3 | |
| 0.0.11 | 0 / 3 | |
| 0.0.10 | 0 / 2 | |
| 0.0.9 | 0 / 2 | |
| 0.0.5 | 0 / 2 | |
| 0.0.4 | 0 / 2 | |
| 0.0.3 | 0 / 2 | |
| 0.0.2 | 0 / 2 | |
| 2.0.0-rc.3 | 0 / 7 | |
| 2.0.0-rc.2 | 0 / 7 | |
| 2.0.0-rc.1 | 0 / 7 | |
| 2.0.0-rc.0 | 0 / 7 | |
| 2.0.0-canary.20260120 | 0 / 4 | |
| 2.0.0-canary-20260116 | 0 / 4 | |
| 2.0.0-beta.9 | 0 / 5 | |
| 2.0.0-beta.8 | 0 / 4 | |
| 2.0.0-beta.7 | 0 / 4 | |
| 2.0.0-beta.6 | 0 / 4 | |
| 2.0.0-beta.5 | 0 / 4 | |
| 2.0.0-beta.4 | 0 / 4 | |
| 2.0.0-beta.3 | 0 / 4 |
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
2 findingsMatched 4 signal(s), weighted score 8: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: hardfist, iwanabethatguy. • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'iwanabethatguy' owns 27 packages, ≥70% share a templated name shape. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_KEYWORDS] No keywords declared.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.