@quenty/multipleclickutils
Utility library for detecting multiple clicks or taps. Not good UX, but good for opening up a debug menus
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): High-trust publisher with 1116 approvals; no material changes in this version; dormancy alone is insufficient signal. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard only-allow pnpm enforcer used across the entire NevermoreEngine monorepo; not malicious. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox/Lua package; deps are consumed by the Roblox loader, not imported as JS modules. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same as above — Roblox loader pattern, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same as above — Roblox loader pattern, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Same as above — Roblox loader pattern, stable false positive for this package. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 13.28.3 | 4 / 0 | |
| 13.28.2 | 4 / 0 | |
| 13.28.1 | 4 / 0 | |
| 13.25.0 | 4 / 0 | |
| 13.24.0 | 4 / 0 | |
| 13.23.0 | 4 / 0 | |
| 13.22.0 | 4 / 0 | |
| 13.21.2 | 4 / 0 | |
| 13.21.1 | 4 / 0 | |
| 13.21.0 | 4 / 0 | |
| 13.20.3 | 4 / 0 | |
| 13.20.1 | 4 / 0 | |
| 13.20.0 | 4 / 0 | |
| 13.19.0 | 4 / 0 | |
| 13.18.1 | 4 / 0 | |
| 13.18.0 | 4 / 0 | |
| 13.17.3 | 4 / 0 | |
| 13.17.2 | 4 / 0 | |
| 13.17.1 | 4 / 0 | |
| 13.17.0 | 4 / 0 | |
| 13.16.2 | 4 / 0 | |
| 13.16.1 | 4 / 0 | |
| 13.16.0 | 4 / 0 | |
| 13.15.0 | 4 / 0 | |
| 13.14.0 | 4 / 0 | |
| 13.13.0 | 4 / 0 | |
| 13.12.0 | 4 / 0 | |
| 13.11.1 | 4 / 0 | |
| 13.11.0 | 4 / 0 | |
| 13.10.0 | 4 / 0 | |
| 13.9.0 | 4 / 0 | |
| 13.8.0 | 4 / 0 | |
| 13.7.0 | 4 / 0 | |
| 13.6.0 | 4 / 0 | |
| 13.5.0 | 4 / 0 | |
| 13.4.0 | 4 / 0 | |
| 13.3.0 | 4 / 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.0
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.