@stackwright/cli
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with 27 approved versions; lack of Sigstore attestation is a process gap, not a security signal. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @stackwright/cli is a scoped CLI tool for the Stackwright framework, not a typosquat of joi. The name similarity is coincidental and the package has clear, legitimate identity. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is explicitly declared as a runtime dependency in package.json; the phantom-dep finding is a false positive from static import analysis not tracing all usage paths. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.8.6 | 6 / 10 | |
| 0.8.5 | 6 / 10 | |
| 0.8.4 | 6 / 11 | |
| 0.8.3 | 11 / 6 | |
| 0.8.2 | 11 / 6 | |
| 0.8.0 | 11 / 6 | |
| 0.7.0 | 9 / 6 | |
| 0.6.0 | 9 / 6 | |
| 0.5.1 | 9 / 6 | |
| 0.5.0 | 9 / 6 | |
| 0.4.0 | 10 / 5 | |
| 0.3.0 | 10 / 5 | |
| 0.2.2 | 10 / 5 | |
| 0.2.1 | 10 / 5 | |
| 0.2.0 | 10 / 5 |
v0.8.6
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: stackwright.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
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: stackwright.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.