@quenty/binder
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): Git URL dep is from the same author's org (quentystudios); used as test infrastructure, not a supply-chain risk. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/linkutils | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/servicebag | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/canceltoken | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/instanceutils | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox/Lua monorepo; deps are declared for tooling, not JS imports. False positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/brio | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/table | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quentystudios/jest-lua | AI (phantom-deps): Test tooling dep referenced in config; not a JS import. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/nevermore-test-runner | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard package-manager enforcer; benign and consistent across all NevermoreEngine packages. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 14.35.0 | 15 / 0 | |
| 14.34.0 | 15 / 0 | |
| 14.33.0 | 15 / 0 | |
| 14.31.0 | 15 / 0 | |
| 14.29.0 | 13 / 0 | |
| 14.27.1 | 13 / 0 | |
| 14.27.0 | 13 / 0 | |
| 14.26.1 | 13 / 0 | |
| 14.26.0 | 13 / 0 | |
| 14.25.7 | 13 / 0 | |
| 14.25.6 | 12 / 0 | |
| 14.25.5 | 12 / 0 | |
| 14.25.4 | 12 / 0 | |
| 14.25.3 | 12 / 0 | |
| 14.25.2 | 12 / 0 | |
| 14.25.1 | 12 / 0 | |
| 14.25.0 | 12 / 0 | |
| 14.24.0 | 12 / 0 | |
| 14.23.0 | 11 / 0 | |
| 14.22.0 | 11 / 0 | |
| 14.21.1 | 11 / 0 | |
| 14.21.0 | 11 / 0 | |
| 14.20.0 | 10 / 0 |
v14.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.25.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.25.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.25.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.23.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.