@quenty/memoize
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): Part of NevermoreEngine monorepo with 1116 approved packages; batch releases after gaps are normal for this publisher. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a benign package-manager enforcement script; stable pattern for this monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/tuple | AI (phantom-deps): Same-org monorepo dep; indirect import pattern is expected. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo dep; indirect import pattern is expected. | ai | |
| phantom-deps | phantom-dep:@quenty/lrucache | AI (phantom-deps): Same-org monorepo dep; indirect import pattern is expected. | ai | |
| phantom-deps | phantom-dep:@quenty/typeutils | AI (phantom-deps): Same-org monorepo dep; indirect import pattern is expected. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.9.1 | 4 / 0 | |
| 1.9.0 | 4 / 0 | |
| 1.8.0 | 4 / 0 | |
| 1.7.3 | 4 / 0 | |
| 1.7.2 | 4 / 0 | |
| 1.7.1 | 4 / 0 | |
| 1.7.0 | 3 / 0 |
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.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.
v1.8.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.
v1.7.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.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.