@stackwright/build-scripts
Build-time scripts for Stackwright projects (prebuild image processing, YAML compilation)
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is consistent with tsup bundling the newly added @stackwright/types dependency into dist output. No obfuscation or payload signals present. | ai | |
| provenance | no-provenance | AI (provenance): Internal Stackwright tooling package; lack of Sigstore provenance is a minor gap but not a blocker given the consistent org identity and clean publisher track record. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.7.2 | 4 / 4 | |
| 0.7.1 | 4 / 5 | |
| 0.7.0 | 3 / 5 | |
| 0.6.0 | 3 / 5 | |
| 0.5.0 | 3 / 5 | |
| 0.4.0 | 2 / 5 | |
| 0.3.0 | 2 / 5 | |
| 0.2.1 | 2 / 5 | |
| 0.2.0 | 2 / 5 | |
| 0.1.1 | 1 / 5 |
v0.7.2
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.