@quenty/color3utils
Utility methods for Roblox Color3 values
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): High-volume trusted publisher with 550 approved packages; dormancy likely reflects normal release cadence for this monorepo package. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard package-manager enforcement pattern; stable across all versions of this monorepo package. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Same-org Roblox/Lua package; imports resolved at runtime via @quenty/loader, not via static JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same-org Roblox/Lua package; runtime loader pattern, not static JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org Roblox/Lua package; runtime loader pattern, not static JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/blend | AI (phantom-deps): Same-org Roblox/Lua package; runtime loader pattern, not static JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same-org Roblox/Lua package; runtime loader pattern, not static JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/math | AI (phantom-deps): Same-org Roblox/Lua package; runtime loader pattern, not static JS imports. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 11.35.0 | 6 / 0 | |
| 11.34.2 | 6 / 0 | |
| 11.34.1 | 6 / 0 | |
| 11.28.2 | 6 / 0 | |
| 11.27.0 | 6 / 0 | |
| 11.26.0 | 6 / 0 | |
| 11.25.0 | 6 / 0 | |
| 11.24.1 | 6 / 0 | |
| 11.24.0 | 6 / 0 | |
| 11.23.1 | 6 / 0 | |
| 11.23.0 | 6 / 0 | |
| 11.22.4 | 6 / 0 | |
| 11.21.0 | 6 / 0 | |
| 11.20.0 | 6 / 0 | |
| 11.19.1 | 6 / 0 | |
| 11.19.0 | 6 / 0 |
v11.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.34.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.
v11.34.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.
v11.28.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.
v11.27.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.
v11.26.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.
v11.25.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.
v11.24.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.
v11.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.22.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.