@quenty/settings-inputkeymap
Input key map setting saving for players
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): npx only-allow pnpm is a standard pnpm-enforcement preinstall; stable pattern across this monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Roblox/Lua monorepo; deps loaded via Lua loader, not Node require — phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@quenty/table | AI (phantom-deps): Same monorepo Lua-loader pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same monorepo Lua-loader pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/string | AI (phantom-deps): Same monorepo Lua-loader pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/settings | AI (phantom-deps): Same monorepo Lua-loader pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/enumutils | AI (phantom-deps): Same monorepo Lua-loader pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/inputmode | AI (phantom-deps): Same monorepo Lua-loader pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/jsonutils | AI (phantom-deps): Same monorepo Lua-loader pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Same monorepo Lua-loader pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/servicebag | AI (phantom-deps): Same monorepo Lua-loader pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quentystudios/jest-lua | AI (phantom-deps): Referenced in config files for Lua test runner; not a Node import — stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/inputkeymaputils | AI (phantom-deps): Same monorepo Lua-loader pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/nevermore-test-runner | AI (phantom-deps): Same monorepo Lua-loader pattern; stable false positive. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 10.53.0 | 13 / 0 | |
| 10.50.0 | 13 / 0 | |
| 10.40.1 | 11 / 0 | |
| 10.40.0 | 11 / 0 | |
| 10.39.1 | 11 / 0 | |
| 10.39.0 | 11 / 0 | |
| 10.38.0 | 11 / 0 | |
| 10.37.1 | 11 / 0 | |
| 10.37.0 | 11 / 0 | |
| 10.36.4 | 11 / 0 | |
| 10.36.3 | 11 / 0 | |
| 10.36.2 | 11 / 0 | |
| 10.36.1 | 11 / 0 | |
| 10.36.0 | 11 / 0 | |
| 10.35.4 | 11 / 0 | |
| 10.35.3 | 11 / 0 | |
| 10.35.2 | 11 / 0 | |
| 10.35.1 | 11 / 0 | |
| 10.35.0 | 11 / 0 | |
| 10.34.1 | 11 / 0 | |
| 10.34.0 | 11 / 0 | |
| 10.33.0 | 11 / 0 | |
| 10.32.0 | 11 / 0 | |
| 10.31.0 | 11 / 0 | |
| 10.30.0 | 11 / 0 | |
| 10.29.2 | 11 / 0 | |
| 10.29.1 | 11 / 0 | |
| 10.29.0 | 11 / 0 | |
| 10.28.1 | 11 / 0 | |
| 10.28.0 | 11 / 0 | |
| 10.27.1 | 11 / 0 | |
| 10.27.0 | 11 / 0 | |
| 10.26.0 | 11 / 0 |
v10.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.50.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.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.36.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.36.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.36.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.35.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.35.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.35.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.