@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, so a manually published version cannot be tied back to a reviewed commit.
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 46 of 46)
| 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 | |
| 13.17.3 | 5 / 0 | |
| 13.17.2 | 5 / 0 | |
| 13.17.1 | 5 / 0 | |
| 13.17.0 | 5 / 0 | |
| 13.16.2 | 5 / 0 | |
| 13.16.1 | 5 / 0 | |
| 13.16.0 | 5 / 0 | |
| 13.15.0 | 5 / 0 | |
| 13.14.0 | 5 / 0 | |
| 13.13.0 | 5 / 0 | |
| 13.12.0 | 5 / 0 | |
| 13.11.1 | 5 / 0 | |
| 13.11.0 | 5 / 0 | |
| 13.10.0 | 5 / 0 | |
| 13.9.1 | 5 / 0 | |
| 13.9.0 | 5 / 0 | |
| 13.8.1 | 5 / 0 | |
| 13.8.0 | 5 / 0 | |
| 13.7.0 | 5 / 0 | |
| 13.6.0 | 5 / 0 | |
| 13.5.0 | 5 / 0 | |
| 13.4.0 | 5 / 0 | |
| 13.3.0 | 5 / 0 | |
| 13.2.0 | 5 / 0 | |
| 13.1.0 | 5 / 0 | |
| 13.0.0 | 5 / 0 |
v13.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.