shipitjs
npm package release management tool
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
hide_o_55
Keywords
release managementnpmgithg
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads local ./steps/ modules by name — bounded internal plugin pattern, not arbitrary external input. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Release management CLI legitimately shells out to npm/git; expected behavior for this package type. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 6 / 0 |
v0.3.2
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.