@quenty/canceltoken
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 1116 approved releases with zero rejections; dormancy gap is not indicative of takeover given this track record. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for Roblox Lua packages. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for Roblox Lua packages. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard package manager enforcement pattern used across this monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for Roblox Lua packages. | ai | |
| phantom-deps | phantom-dep:@quenty/ducktype | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for Roblox Lua packages. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for Roblox Lua packages. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 11.19.1 | 5 / 0 | |
| 11.19.0 | 5 / 0 | |
| 11.18.0 | 5 / 0 | |
| 11.14.0 | 5 / 0 | |
| 11.13.4 | 5 / 0 | |
| 11.13.3 | 5 / 0 | |
| 11.13.2 | 5 / 0 | |
| 11.13.1 | 5 / 0 | |
| 11.13.0 | 5 / 0 | |
| 11.12.1 | 5 / 0 | |
| 11.12.0 | 5 / 0 |
v11.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.