@quenty/brio
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:@quentystudios/jest-lua | AI (npm-metadata): Same-org test dependency from quentystudios; used for Lua test tooling, not a supply-chain risk for consumers. | ai | |
| dependencies | unvetted-dep:@quentystudios/jest-lua | AI (dependencies): Same-org (quentystudios) test runner; phantom dep not imported by consumers. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Roblox/Lua package; JS import analysis doesn't apply to Lua module resolution. | ai | |
| phantom-deps | phantom-dep:@quenty/table | AI (phantom-deps): Roblox/Lua package; JS import analysis doesn't apply to Lua module resolution. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Roblox/Lua package; JS import analysis doesn't apply to Lua module resolution. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard package-manager enforcement script; no code execution risk. | ai | |
| phantom-deps | phantom-dep:@quenty/steputils | AI (phantom-deps): Roblox/Lua package; JS import analysis doesn't apply to Lua module resolution. | ai | |
| phantom-deps | phantom-dep:@quentystudios/jest-lua | AI (phantom-deps): Referenced in config files as documented; Lua test runner, not a JS import. | ai | |
| phantom-deps | phantom-dep:@quenty/nevermore-test-runner | AI (phantom-deps): Roblox/Lua package; JS import analysis doesn't apply to Lua module resolution. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Roblox/Lua package; JS import analysis doesn't apply to Lua module resolution. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox/Lua package; JS import analysis doesn't apply to Lua module resolution. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 14.29.1 | 8 / 0 | |
| 14.29.0 | 8 / 0 | |
| 14.28.0 | 8 / 0 | |
| 14.25.0 | 8 / 0 | |
| 14.22.2 | 6 / 0 | |
| 14.22.0 | 6 / 0 | |
| 14.21.0 | 6 / 0 | |
| 14.20.5 | 6 / 0 | |
| 14.20.4 | 6 / 0 | |
| 14.20.3 | 6 / 0 | |
| 14.20.2 | 6 / 0 | |
| 14.20.1 | 6 / 0 | |
| 14.20.0 | 6 / 0 | |
| 14.19.0 | 6 / 0 | |
| 14.18.1 | 6 / 0 | |
| 14.18.0 | 6 / 0 |
v14.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.