@quenty/uiobjectutils
UI object utils library for Roblox
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@quenty/rx | AI (dependencies): Same @quenty org scope; consistent with the rest of the Nevermore package family dependencies. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox/Lua package; deps declared for tooling but not JS-imported. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/brio | AI (phantom-deps): Same as above — Lua package pattern, not a real phantom dep. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard package manager enforcement pattern used across the NevermoreEngine monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/enumutils | AI (phantom-deps): Same as above — Lua package pattern, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@quenty/instanceutils | AI (phantom-deps): Same as above — Lua package pattern, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same as above — Lua package pattern, not a real phantom dep. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 6.28.2 | 5 / 0 | |
| 6.28.1 | 5 / 0 | |
| 6.28.0 | 5 / 0 | |
| 6.27.0 | 5 / 0 | |
| 6.25.0 | 5 / 0 | |
| 6.23.1 | 5 / 0 | |
| 6.23.0 | 5 / 0 | |
| 6.21.0 | 5 / 0 | |
| 6.19.6 | 5 / 0 | |
| 6.19.3 | 5 / 0 | |
| 6.19.2 | 5 / 0 | |
| 6.19.1 | 5 / 0 | |
| 6.17.0 | 5 / 0 |
v6.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.19.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.