@stratusjs/core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit runtime dependency, not a real concern. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @stratusjs/core is part of the established Stratus framework, not a typosquat of cors. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 2 / 0 | |
| 0.9.2 | 2 / 0 | |
| 0.9.1 | 2 / 0 | |
| 0.9.0 | 2 / 0 | |
| 0.8.1 | 2 / 0 | |
| 0.8.0 | 2 / 0 |
v0.9.2
2 findingsThis version was published by a different npm account (chadwickmeyer) than the most recent previously approved version (apocist) on 2025-04-10. It has since remained available on npm for 464 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
2 findingsThis version was published by a different npm account (chadwickmeyer) than the most recent previously approved version (apocist) on 2025-02-24. It has since remained available on npm for 509 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
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.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.