@quenty/overriddenproperty
Sets properties on the client and then replicates them to the server
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 |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a standard monorepo package-manager guard; stable across all quenty/NevermoreEngine packages. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org Roblox/Lua package; phantom-dep heuristic unreliable for Lua-targeted npm packages. | ai | |
| phantom-deps | phantom-dep:@quenty/throttle | AI (phantom-deps): Same-org Roblox/Lua package; phantom-dep heuristic unreliable for Lua-targeted npm packages. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Same-org Roblox/Lua package; phantom-dep heuristic unreliable for Lua-targeted npm packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 10.14.2 | 3 / 0 | |
| 10.14.1 | 3 / 0 | |
| 10.14.0 | 3 / 0 | |
| 10.10.2 | 3 / 0 | |
| 10.10.1 | 3 / 0 | |
| 10.10.0 | 3 / 0 |
v10.14.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.
v10.14.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.
v10.14.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.
v10.10.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.
v10.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.