@quenty/rbxasset
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org dependency used as a runtime dep in this Roblox utility package; stable false positive. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm enforcer; standard monorepo pattern, stable for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 5.12.0 | 1 / 0 | |
| 5.11.0 | 1 / 0 | |
| 5.10.3 | 1 / 0 | |
| 5.10.2 | 1 / 0 | |
| 5.10.1 | 1 / 0 | |
| 5.10.0 | 1 / 0 | |
| 5.9.0 | 1 / 0 |
v5.12.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.
v5.11.0
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.3
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.2
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.