@quenty/radial-image
Quenty's radial image system
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 with coordinated releases; dormancy followed by batch publish is expected for this org. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Same-org monorepo package; Lua/Roblox imports not detectable by Node.js static analysis. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same-org monorepo package; Lua/Roblox imports not detectable by Node.js static analysis. | ai | |
| phantom-deps | phantom-dep:@quenty/math | AI (phantom-deps): Same-org monorepo package; Lua/Roblox imports not detectable by Node.js static analysis. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard pnpm-enforcement pattern used across the NevermoreEngine monorepo; not malicious. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo package; Lua/Roblox imports not detectable by Node.js static analysis. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Same-org monorepo package; Lua/Roblox imports not detectable by Node.js static analysis. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same-org monorepo package; Lua/Roblox imports not detectable by Node.js static analysis. | ai | |
| phantom-deps | phantom-dep:@quenty/blend | AI (phantom-deps): Same-org monorepo package; Lua/Roblox imports not detectable by Node.js static analysis. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 9.36.0 | 7 / 0 | |
| 9.35.2 | 7 / 0 | |
| 9.33.0 | 7 / 0 | |
| 9.31.0 | 7 / 0 | |
| 9.29.2 | 7 / 0 | |
| 9.26.1 | 7 / 0 | |
| 9.26.0 | 7 / 0 | |
| 9.24.0 | 7 / 0 | |
| 9.23.3 | 7 / 0 | |
| 9.23.2 | 7 / 0 | |
| 9.23.1 | 7 / 0 | |
| 9.21.0 | 7 / 0 | |
| 9.20.1 | 7 / 0 | |
| 9.20.0 | 7 / 0 |
v9.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.35.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.
v9.33.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.
v9.31.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.
v9.29.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.
v9.26.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.
v9.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.
v9.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.