@stacksjs/security
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo lockstep releases across @stacksjs/* packages publish in rapid succession routinely. | ai | |
| dependencies | unvetted-dep:@stacksjs/env | AI (dependencies): First-party same-org monorepo sibling package. | ai | |
| dependencies | unvetted-dep:@stacksjs/validation | AI (dependencies): First-party same-org monorepo sibling package. | ai | |
| dependencies | unvetted-dep:ts-security-crypto | AI (dependencies): New minor crypto dep, no exec/exfil behavior; part of routine Stacks framework release cadence. | ai | |
| phantom-deps | phantom-dep:@stacksjs/config | AI (phantom-deps): Same-org sibling package, monorepo pattern. | ai | |
| phantom-deps | phantom-dep:crypto-js | AI (phantom-deps): Used indirectly via config; benign for this package. | ai | |
| phantom-deps | phantom-dep:@stacksjs/validation | AI (phantom-deps): Same-org sibling package, monorepo pattern. | ai | |
| phantom-deps | phantom-dep:js-base64 | AI (phantom-deps): Used indirectly via config; benign for this package. | ai | |
| phantom-deps | phantom-dep:@stacksjs/env | AI (phantom-deps): Same-org sibling package, monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@stacksjs/types | AI (phantom-deps): Same-org sibling package, monorepo pattern. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 0.70.170 | 1 / 5 | |
| 0.70.60 | 1 / 5 | |
| 0.70.44 | 1 / 5 | |
| 0.70.42 | 1 / 5 | |
| 0.70.37 | 1 / 5 | |
| 0.70.35 | 1 / 5 | |
| 0.70.28 | 1 / 5 | |
| 0.70.27 | 1 / 5 | |
| 0.70.26 | 1 / 5 | |
| 0.70.23 | 0 / 7 | |
| 0.70.22 | 0 / 7 | |
| 0.70.21 | 0 / 7 | |
| 0.70.19 | 0 / 7 | |
| 0.70.18 | 0 / 7 | |
| 0.70.17 | 0 / 7 | |
| 0.70.16 | 0 / 7 | |
| 0.70.15 | 0 / 7 | |
| 0.70.14 | 0 / 7 | |
| 0.70.13 | 0 / 7 | |
| 0.70.12 | 0 / 7 | |
| 0.70.11 | 0 / 7 | |
| 0.70.10 | 0 / 7 | |
| 0.70.9 | 0 / 7 | |
| 0.70.8 | 0 / 7 | |
| 0.70.7 | 0 / 7 | |
| 0.70.6 | 0 / 7 | |
| 0.70.5 | 0 / 7 | |
| 0.70.4 | 0 / 7 | |
| 0.70.3 | 0 / 7 | |
| 0.70.2 | 0 / 7 | |
| 0.70.1 | 0 / 7 | |
| 0.70.0 | 0 / 7 | |
| 0.69.3 | 0 / 7 | |
| 0.69.2 | 0 / 7 | |
| 0.69.1 | 0 / 7 | |
| 0.68.0 | 6 / 1 | |
| 0.65.0 | 0 / 0 | |
| 0.64.0 | 6 / 1 |
v0.70.170
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.60
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.