@quenty/geometryutils
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): Established NevermoreEngine monorepo package; dormancy reflects project cadence, not account takeover. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a standard package manager enforcement script; stable pattern across this monorepo's packages. | ai | |
| phantom-deps | phantom-dep:@quenty/draw | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 6.14.1 | 2 / 0 | |
| 6.14.0 | 2 / 0 | |
| 6.12.0 | 2 / 0 | |
| 6.9.5 | 2 / 0 | |
| 6.9.4 | 2 / 0 | |
| 6.9.3 | 2 / 0 | |
| 6.9.2 | 2 / 0 | |
| 6.9.1 | 2 / 0 | |
| 6.9.0 | 2 / 0 |
v6.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.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.
v6.12.0
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.5
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.4
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.