@stackwright/core
Core framework for building applications from YAML configuration
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:@fontsource/montserrat-alternates | AI (phantom-deps): Font package loaded by convention; referenced in config. | ai | |
| phantom-deps | phantom-dep:@emotion/cache | AI (phantom-deps): Styling framework loaded by convention; referenced in config. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Styling framework loaded by convention; referenced in config. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Styling framework loaded by convention; referenced in config. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Peer dependency loaded by convention in React framework context. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped package loaded by convention; stable pattern. | ai | |
| phantom-deps | phantom-dep:prismjs | AI (phantom-deps): prismjs is a declared runtime dep used via config/type references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): js-yaml is listed as a runtime dependency and used in YAML config parsing; phantom-dep heuristic misfires here. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @stackwright/core package; name reflects its own framework, not an impersonation of cors. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.8.5 | 8 / 15 | |
| 0.8.4 | 7 / 15 | |
| 0.8.3 | 8 / 15 | |
| 0.8.2 | 8 / 15 | |
| 0.8.1 | 8 / 15 | |
| 0.8.0 | 8 / 15 | |
| 0.7.0 | 7 / 15 | |
| 0.6.0 | 7 / 15 | |
| 0.5.1 | 9 / 16 | |
| 0.5.0 | 9 / 16 | |
| 0.4.1 | 12 / 12 | |
| 0.4.0 | 12 / 5 | |
| 0.3.0 | 12 / 5 | |
| 0.2.2 | 12 / 5 | |
| 0.2.1 | 12 / 5 | |
| 0.2.0 | 12 / 5 |
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
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.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.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.