@quenty/statestack
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:@quenty/maid | AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard package-manager enforcement pattern used across this monorepo; not malicious. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox/Lua monorepo; deps may be consumed by Lua loader, not JS imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/brio | AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 14.31.0 | 7 / 0 | |
| 14.30.0 | 7 / 0 | |
| 14.24.0 | 7 / 0 | |
| 14.23.1 | 7 / 0 | |
| 14.23.0 | 7 / 0 | |
| 14.22.7 | 7 / 0 | |
| 14.22.6 | 7 / 0 | |
| 14.22.5 | 7 / 0 | |
| 14.22.4 | 7 / 0 | |
| 14.22.3 | 7 / 0 | |
| 14.22.2 | 7 / 0 | |
| 14.22.1 | 7 / 0 | |
| 14.22.0 | 7 / 0 | |
| 14.21.0 | 6 / 0 | |
| 14.20.0 | 6 / 0 | |
| 14.19.1 | 6 / 0 | |
| 14.19.0 | 6 / 0 | |
| 14.18.3 | 6 / 0 | |
| 14.18.2 | 6 / 0 | |
| 14.18.1 | 6 / 0 | |
| 14.18.0 | 6 / 0 | |
| 14.17.2 | 6 / 0 | |
| 14.17.1 | 6 / 0 | |
| 14.17.0 | 6 / 0 | |
| 14.16.0 | 6 / 0 | |
| 14.15.0 | 6 / 0 | |
| 14.14.0 | 6 / 0 | |
| 14.13.0 | 6 / 0 | |
| 14.12.1 | 6 / 0 | |
| 14.12.0 | 6 / 0 | |
| 14.11.0 | 6 / 0 | |
| 14.10.2 | 6 / 0 | |
| 14.10.1 | 6 / 0 | |
| 14.10.0 | 6 / 0 | |
| 14.9.1 | 6 / 0 | |
| 14.9.0 | 6 / 0 | |
| 14.8.0 | 6 / 0 | |
| 14.7.0 | 6 / 0 | |
| 14.6.0 | 6 / 0 | |
| 14.5.0 | 6 / 0 | |
| 14.4.0 | 6 / 0 | |
| 14.3.0 | 6 / 0 | |
| 14.2.0 | 6 / 0 | |
| 14.1.0 | 6 / 0 | |
| 14.0.0 | 6 / 0 |
v14.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.