impit
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 | missing-githead | AI (provenance): Package has SLSA provenance attestation which supersedes gitHead as a supply-chain integrity signal. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Only enforces pnpm package manager; no arbitrary code execution. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): Runs 'ldd --version' to detect musl libc for native binary selection; benign napi-rs pattern. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Same musl-detection usage; stable false positive for this native binding package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads NAPI_RS_NATIVE_LIBRARY_PATH env var override; standard napi-rs escape hatch pattern. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 0.14.1 | 0 / 11 | |
| 0.14.0 | 0 / 11 | |
| 0.13.1 | 0 / 11 | |
| 0.13.0 | 0 / 11 | |
| 0.12.0 | 0 / 11 | |
| 0.11.0 | 0 / 11 | |
| 0.10.1 | 0 / 11 | |
| 0.10.0 | 0 / 11 | |
| 0.9.2 | 0 / 11 | |
| 0.9.1 | 0 / 11 | |
| 0.9.0 | 0 / 11 | |
| 0.8.2 | 0 / 11 | |
| 0.8.1 | 0 / 11 | |
| 0.8.0 | 0 / 11 | |
| 0.7.6 | 0 / 11 | |
| 0.7.5 | 0 / 11 | |
| 0.7.4 | 0 / 11 | |
| 0.7.3 | 0 / 11 | |
| 0.7.2 | 0 / 11 | |
| 0.7.1 | 0 / 11 | |
| 0.7.0 | 0 / 10 | |
| 0.6.1 | 0 / 10 | |
| 0.6.0 | 0 / 10 | |
| 0.5.4 | 0 / 7 | |
| 0.5.3 | 0 / 7 | |
| 0.5.2 | 0 / 7 | |
| 0.5.1 | 0 / 7 | |
| 0.5.0 | 0 / 6 | |
| 0.4.7 | 0 / 5 | |
| 0.4.6 | 0 / 5 | |
| 0.4.5 | 0 / 5 | |
| 0.4.4 | 0 / 5 | |
| 0.4.3 | 0 / 5 | |
| 0.4.2 | 0 / 5 |
v0.14.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This 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.
v0.14.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.
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.