@quenty/gameversionutils
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 |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a package-manager guard, not arbitrary code execution. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Same-org Lua sibling package; Lua imports aren't detected by JS import scanner. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org Lua sibling package; Lua imports aren't detected by JS import scanner. | ai | |
| phantom-deps | phantom-dep:@quenty/instanceutils | AI (phantom-deps): Same-org Lua sibling package; Lua imports aren't detected by JS import scanner. | ai | |
| phantom-deps | phantom-dep:@quenty/nevermoreclimanifest | AI (phantom-deps): Same-org Lua sibling package; Lua imports aren't detected by JS import scanner. | ai | |
| phantom-deps | phantom-dep:@quenty/nevermore-test-runner | AI (phantom-deps): Same-org Lua sibling package; Lua imports aren't detected by JS import scanner. | ai | |
| phantom-deps | phantom-dep:@quentystudios/jest-lua | AI (phantom-deps): Test tooling dep from same publisher ecosystem, not directly imported by design. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.6.1 | 6 / 0 | |
| 3.6.0 | 6 / 0 | |
| 3.5.0 | 0 / 0 | |
| 3.4.2 | 0 / 0 | |
| 3.4.1 | 0 / 0 | |
| 3.4.0 | 0 / 0 |
v3.6.1
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.