rhachet-artifact
3
Versions
—
License
Yes
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
uladkasach
Keywords
artifactrhachet
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): Husky git-hooks setup; only runs when .git dir exists, safe for downstream consumers. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI/CD is consistent with SLSA attestation; legitimate automation pattern for this package. | ai | |
| phantom-deps | phantom-dep:helpful-errors | AI (phantom-deps): helpful-errors is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
v1.0.3
2 findings
HIGH
Publisher changed: uladkasach → GitHub Actions (on 2026-01-05)
provenance
This version was published by a different npm account than previous versions on 2026-01-05. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.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.
v1.0.0
2 findings
HIGH
Package has 'postinstall' script
install-scripts
Script: [ -d .git ] && npm run prepare:husky || exit 0
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.