@c-rex/contexts
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:next | AI (phantom-deps): next is a framework dep referenced in config; phantom-dep heuristic fires on config-only references, not a real concern. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a peer dep referenced in config files; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@c-rex/core | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo internal packages. | ai | |
| phantom-deps | phantom-dep:@c-rex/services | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo internal packages. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.1.21 | 8 / 8 | |
| 0.1.20 | 8 / 8 | |
| 0.1.19 | 8 / 8 | |
| 0.1.17 | 8 / 8 | |
| 0.1.16 | 8 / 8 | |
| 0.1.15 | 8 / 8 | |
| 0.1.13 | 8 / 8 | |
| 0.0.7 | 3 / 8 |
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.