@quenty/ugcsanitize
Sanitizes UGC hats and other items
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Large monorepo; irregular publish cadence is expected. Publisher has 887 approved packages with no rejections. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Roblox/Lua monorepo; deps consumed by Lua toolchain, not Node require. Same-org scope. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same rationale: Lua monorepo deps not imported via Node require. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard pnpm-enforcement preinstall; stable pattern across this monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Same rationale: Lua monorepo deps not imported via Node require. | ai | |
| phantom-deps | phantom-dep:@quenty/instanceutils | AI (phantom-deps): Same rationale: Lua monorepo deps not imported via Node require. | ai | |
| phantom-deps | phantom-dep:@quenty/string | AI (phantom-deps): Same rationale: Lua monorepo deps not imported via Node require. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.17.0 | 5 / 0 | |
| 1.16.2 | 5 / 0 | |
| 1.16.0 | 5 / 0 | |
| 1.15.0 | 5 / 0 | |
| 1.13.0 | 5 / 0 | |
| 1.12.0 | 5 / 0 | |
| 1.11.0 | 5 / 0 | |
| 1.9.1 | 5 / 0 | |
| 1.9.0 | 5 / 0 | |
| 1.8.0 | 5 / 0 | |
| 1.7.7 | 5 / 0 | |
| 1.7.6 | 5 / 0 | |
| 1.7.5 | 5 / 0 | |
| 1.7.4 | 5 / 0 | |
| 1.7.3 | 5 / 0 | |
| 1.7.2 | 5 / 0 | |
| 1.7.1 | 5 / 0 | |
| 1.7.0 | 5 / 0 | |
| 1.6.0 | 5 / 0 | |
| 1.5.1 | 5 / 0 | |
| 1.5.0 | 5 / 0 |
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
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.
v1.16.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.
v1.15.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.
v1.13.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.
v1.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.
v1.11.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.
v1.9.1
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.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.