@quenty/promisemaid
Utility methods around promises and maids
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@quentystudios/jest-lua | AI (phantom-deps): Test tooling dep in Lua monorepo; not JS-imported by design. | ai | |
| dependencies | unvetted-dep:@quentystudios/jest-lua | AI (dependencies): Companion test framework from trusted publisher's ecosystem. | ai | |
| phantom-deps | phantom-dep:@quenty/nevermore-test-runner | AI (phantom-deps): Same-org test dep, not directly imported by design. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): High-trust publisher with 1116 approved packages; dormancy gap is not indicative of takeover given clean diff and established repo. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a standard package manager enforcement tool; stable pattern across all @quenty/* packages. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same as above — Lua package, no JS imports expected. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same as above — Lua package, no JS imports expected. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Roblox/Lua package; deps are declared for the Nevermore loader, not JS imports. Stable false positive. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 5.21.0 | 5 / 0 | |
| 5.19.0 | 3 / 0 | |
| 5.18.1 | 3 / 0 | |
| 5.18.0 | 3 / 0 | |
| 5.17.0 | 3 / 0 | |
| 5.12.6 | 3 / 0 | |
| 5.12.4 | 3 / 0 | |
| 5.12.3 | 3 / 0 | |
| 5.12.2 | 3 / 0 | |
| 5.12.1 | 3 / 0 | |
| 5.12.0 | 3 / 0 | |
| 5.11.0 | 3 / 0 | |
| 5.10.4 | 3 / 0 | |
| 5.10.3 | 3 / 0 | |
| 5.10.2 | 3 / 0 | |
| 5.10.1 | 3 / 0 | |
| 5.10.0 | 3 / 0 | |
| 5.9.0 | 3 / 0 | |
| 5.8.0 | 3 / 0 | |
| 5.7.1 | 3 / 0 | |
| 5.7.0 | 3 / 0 | |
| 5.6.0 | 3 / 0 | |
| 5.5.0 | 3 / 0 | |
| 5.4.0 | 3 / 0 | |
| 5.3.0 | 3 / 0 | |
| 5.2.0 | 3 / 0 | |
| 5.1.0 | 3 / 0 | |
| 5.0.0 | 3 / 0 |
v5.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.