@quenty/servicebag
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-importable, expected false positive. | ai | |
| dependencies | unvetted-dep:@quentystudios/jest-lua | AI (dependencies): Established publisher's own test framework fork, low risk. | ai | |
| phantom-deps | phantom-dep:@quenty/nevermore-test-runner | AI (phantom-deps): Same-org test dep, not directly imported in Lua source. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Large monorepo; batch releases after gaps are normal for this publisher's track record. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a standard monorepo package-manager enforcement script; stable for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Same as above; stable false positive for @quenty/* packages. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Same as above; stable false positive for @quenty/* packages. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Roblox/Lua tooling package; deps declared but not JS-imported is expected for this org's packages. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 11.20.0 | 5 / 0 | |
| 11.18.1 | 3 / 0 | |
| 11.18.0 | 3 / 0 | |
| 11.17.0 | 3 / 0 | |
| 11.16.0 | 3 / 0 | |
| 11.14.0 | 3 / 0 | |
| 11.13.5 | 3 / 0 | |
| 11.13.4 | 3 / 0 | |
| 11.13.3 | 3 / 0 | |
| 11.13.2 | 3 / 0 | |
| 11.13.1 | 3 / 0 | |
| 11.13.0 | 3 / 0 | |
| 11.12.0 | 3 / 0 | |
| 11.11.4 | 3 / 0 | |
| 11.11.3 | 3 / 0 | |
| 11.11.2 | 3 / 0 | |
| 11.11.1 | 3 / 0 | |
| 11.11.0 | 3 / 0 | |
| 11.10.0 | 3 / 0 | |
| 11.9.1 | 3 / 0 | |
| 11.9.0 | 3 / 0 | |
| 11.8.0 | 3 / 0 | |
| 11.7.0 | 3 / 0 | |
| 11.6.0 | 3 / 0 | |
| 11.5.1 | 3 / 0 | |
| 11.5.0 | 3 / 0 | |
| 11.4.0 | 3 / 0 | |
| 11.3.0 | 3 / 0 | |
| 11.2.0 | 3 / 0 | |
| 11.1.0 | 3 / 0 | |
| 11.0.0 | 3 / 0 |
v11.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1
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.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.1
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.