@push.rocks/smartshell
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): No other risk signals; likely a CI environment change, not a supply-chain concern for this well-established package. | ai | |
| dependencies | unvetted-dep:@push.rocks/smartdelay | AI (dependencies): Sibling @push.rocks org package; same publisher lineage, consistent with the rest of the dependency set. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; no provenance is the norm for this publisher org. | ai | |
| phantom-deps | phantom-dep:tree-kill | AI (phantom-deps): tree-kill is a legitimate runtime dep for process management; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/which | AI (phantom-deps): @types/which is a type declaration package; its presence in dependencies without direct import is a stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.5.0 | 5 / 4 | |
| 3.4.0 | 5 / 4 | |
| 3.3.8 | 5 / 4 | |
| 3.3.7 | 5 / 4 | |
| 3.3.6 | 6 / 4 | |
| 3.3.5 | 6 / 4 | |
| 3.3.4 | 6 / 4 | |
| 3.3.3 | 6 / 4 | |
| 3.3.2 | 6 / 4 | |
| 3.3.0 | 6 / 4 | |
| 3.2.4 | 6 / 4 |
v3.5.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: lossless.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.