@quenty/inputmode
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): only-allow pnpm is a standard package manager enforcement script; stable across all versions of this monorepo package. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox/Lua monorepo; deps are consumed by Lua runtime, not Node.js require — phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@quenty/brio | AI (phantom-deps): Same as above — Lua monorepo pattern, not a Node.js import. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same as above — Lua monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@quenty/table | AI (phantom-deps): Same as above — Lua monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same as above — Lua monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Same as above — Lua monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@quenty/ducktype | AI (phantom-deps): Same as above — Lua monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@quenty/servicebag | AI (phantom-deps): Same as above — Lua monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same as above — Lua monorepo pattern. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 13.33.0 | 9 / 0 | |
| 13.32.2 | 9 / 0 | |
| 13.32.1 | 9 / 0 | |
| 13.32.0 | 9 / 0 | |
| 13.31.0 | 9 / 0 | |
| 13.23.1 | 8 / 0 | |
| 13.23.0 | 8 / 0 | |
| 13.22.0 | 8 / 0 | |
| 13.20.0 | 8 / 0 | |
| 13.19.0 | 8 / 0 |
v13.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.23.0
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.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.