@quenty/maid
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:@quentystudios/jest-lua | AI (npm-metadata): Same author's jest-lua fork used for Roblox test tooling, not third-party. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Trusted long-tenured publisher; no behavioral change accompanies the gap. | ai | |
| dependencies | unvetted-dep:@quentystudios/jest-lua | AI (dependencies): Same-org test dependency, phantom-dep confirms config-only use. | ai | |
| phantom-deps | phantom-dep:@quentystudios/jest-lua | AI (phantom-deps): Test dependency referenced in config files; not directly imported in source as expected. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard package manager enforcement pattern; not malicious. | ai | |
| phantom-deps | phantom-dep:@quenty/nevermore-test-runner | AI (phantom-deps): Same-org monorepo test runner dep; phantom-dep heuristic is a false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @quenty/maid is not a plausible typosquat of uuid; different ecosystem and purpose. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a false positive for Roblox Lua packages. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 3.10.0 | 3 / 0 | |
| 3.9.0 | 3 / 0 | |
| 3.7.0 | 3 / 0 | |
| 3.5.3 | 0 / 0 | |
| 3.5.2 | 0 / 0 | |
| 3.5.1 | 0 / 0 | |
| 3.5.0 | 0 / 0 | |
| 3.4.3 | 0 / 0 | |
| 3.4.2 | 0 / 0 | |
| 3.4.1 | 0 / 0 | |
| 3.4.0 | 0 / 0 | |
| 3.3.0 | 0 / 0 | |
| 3.2.0 | 0 / 0 | |
| 3.1.0 | 0 / 0 | |
| 3.0.0 | 0 / 0 |
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.