@quenty/promise
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 monorepo package-manager guard; stable across all @quenty/* packages. | 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/math | 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 | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for Roblox Lua packages. | ai | |
| phantom-deps | phantom-dep:@quenty/deferred | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for Roblox Lua packages. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 10.18.0 | 5 / 0 | |
| 10.17.0 | 5 / 0 | |
| 10.12.4 | 5 / 0 | |
| 10.12.3 | 5 / 0 | |
| 10.12.2 | 4 / 0 | |
| 10.12.1 | 4 / 0 | |
| 10.12.0 | 4 / 0 | |
| 10.11.0 | 4 / 0 |
v10.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.