@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, 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): 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 28 of 28)
| 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 | |
| 11.11.4 | 5 / 0 | |
| 11.11.3 | 5 / 0 | |
| 11.11.2 | 5 / 0 | |
| 11.11.1 | 5 / 0 | |
| 11.11.0 | 5 / 0 | |
| 11.10.0 | 5 / 0 | |
| 11.9.0 | 5 / 0 | |
| 11.8.1 | 5 / 0 | |
| 11.8.0 | 5 / 0 | |
| 11.7.0 | 5 / 0 | |
| 11.6.0 | 5 / 0 | |
| 11.5.0 | 5 / 0 | |
| 11.4.0 | 5 / 0 | |
| 11.3.0 | 5 / 0 | |
| 11.2.0 | 5 / 0 | |
| 11.1.0 | 5 / 0 | |
| 11.0.0 | 5 / 0 |
v11.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.