@conf-ts/compiler-native
Native Rust compiler for conf-ts.
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): Standard NAPI-RS musl detection pattern; hardcoded 'ldd --version' command, not user-controlled. Stable for this native binding package. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): Hardcoded 'ldd --version' for musl/glibc detection in NAPI-RS loader boilerplate. Not a security risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): NAPI_RS_NATIVE_LIBRARY_PATH env var override is documented NAPI-RS behavior for custom binary paths. Standard pattern for native bindings. | ai | |
| phantom-deps | phantom-dep:@napi-rs/cli | AI (phantom-deps): @napi-rs/cli is a build tool invoked via npm scripts ('napi build', 'napi artifacts'), not a runtime import. Phantom dep finding is a false positive for this package type. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.0.8 | 1 / 10 | |
| 0.0.7 | 1 / 10 | |
| 0.0.6 | 1 / 10 | |
| 0.0.5 | 1 / 10 | |
| 0.0.3 | 1 / 10 | |
| 0.0.2 | 1 / 10 |
v0.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.