@quenty/transparencyservice
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): NevermoreEngine monorepo publishes packages in batches; dormancy is expected for individual sub-packages. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard monorepo package-manager enforcement; stable across all NevermoreEngine packages. | ai | |
| phantom-deps | phantom-dep:@quenty/math | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 11.11.1 | 2 / 0 | |
| 11.11.0 | 2 / 0 | |
| 11.10.0 | 2 / 0 | |
| 11.9.3 | 2 / 0 | |
| 11.9.2 | 2 / 0 | |
| 11.9.1 | 2 / 0 |
v11.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.0
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.10.0
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.9.3
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.9.2
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.