@quenty/humanoiddescriptionutils
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
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 standard package-manager enforcement script; stable pattern across this monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org Roblox/Lua package; phantom-dep heuristic unreliable for Lua-based monorepo packages. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same-org Roblox/Lua package; phantom-dep heuristic unreliable for Lua-based monorepo packages. | ai | |
| phantom-deps | phantom-dep:@quenty/insertserviceutils | AI (phantom-deps): Same-org Roblox/Lua package; phantom-dep heuristic unreliable for Lua-based monorepo packages. | ai | |
| phantom-deps | phantom-dep:@quenty/playersservicepromises | AI (phantom-deps): Same-org Roblox/Lua package; phantom-dep heuristic unreliable for Lua-based monorepo packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 10.18.0 | 4 / 0 | |
| 10.17.0 | 4 / 0 | |
| 10.12.5 | 4 / 0 | |
| 10.12.4 | 4 / 0 | |
| 10.12.3 | 4 / 0 | |
| 10.12.2 | 4 / 0 | |
| 10.12.1 | 4 / 0 | |
| 10.12.0 | 4 / 0 | |
| 10.11.1 | 4 / 0 |
v10.18.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.
v10.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.