@quenty/instanceutils
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 (phantom, not directly imported); consistent with Nevermore monorepo tooling pattern. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox Lua package; not imported via Node.js module resolution by design. | ai | |
| phantom-deps | phantom-dep:@quenty/brio | AI (phantom-deps): Roblox Lua package; not imported via Node.js module resolution by design. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Roblox Lua package; not imported via Node.js module resolution by design. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard package manager enforcer; stable pattern across this monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/symbol | AI (phantom-deps): Roblox Lua package; not imported via Node.js module resolution by design. | ai | |
| phantom-deps | phantom-dep:@quentystudios/jest-lua | AI (phantom-deps): Lua test framework; referenced in config files, not Node.js imports by design. | ai | |
| phantom-deps | phantom-dep:@quenty/nevermore-test-runner | AI (phantom-deps): Roblox Lua package; not imported via Node.js module resolution by design. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Roblox Lua package; not imported via Node.js module resolution by design. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 13.29.0 | 7 / 0 | |
| 13.28.0 | 7 / 0 | |
| 13.26.0 | 7 / 0 | |
| 13.25.0 | 7 / 0 | |
| 13.24.0 | 5 / 0 | |
| 13.23.0 | 5 / 0 | |
| 13.22.2 | 5 / 0 | |
| 13.22.1 | 5 / 0 | |
| 13.22.0 | 5 / 0 | |
| 13.21.0 | 5 / 0 | |
| 13.20.6 | 5 / 0 | |
| 13.20.5 | 5 / 0 | |
| 13.20.4 | 5 / 0 | |
| 13.20.3 | 5 / 0 | |
| 13.20.2 | 5 / 0 | |
| 13.20.1 | 5 / 0 | |
| 13.20.0 | 5 / 0 | |
| 13.19.0 | 5 / 0 | |
| 13.18.1 | 5 / 0 | |
| 13.18.0 | 5 / 0 |
v13.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.