rhachet-artifact-git
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Standard husky dev-hooks setup; only runs in git repos, no network fetch or arbitrary code execution. | ai | |
| phantom-deps | phantom-dep:serde-fns | AI (phantom-deps): serde-fns is a runtime dep used in config/type context; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.1.5 | 9 / 27 | |
| 1.1.3 | 9 / 21 | |
| 1.1.2 | 9 / 21 | |
| 1.1.1 | 9 / 24 | |
| 1.0.2 | 9 / 24 | |
| 1.0.0 | 9 / 24 |
v1.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
2 findingsScript: [ -d .git ] && npm run prepare:husky || exit 0
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
2 findingsScript: [ -d .git ] && npm run prepare:husky || exit 0
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsScript: [ -d .git ] && npm run prepare:husky || exit 0
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.