memorizer
memoize a getter of an object
2
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
jonathanongjongleberry
Keywords
memoizememogetter
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): jonathanong → jongleberry is the same author (Jonathan Ong, [email protected]) consolidating npm accounts. Confirmed by package.json author block. Stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jongleberry is the same person as jonathanong per package.json author metadata. Not a third-party takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormant publish in 2015 coincides with account consolidation; no malicious changes introduced. Event is ~9 years old and not a recurring risk. | ai |
v1.0.1
2 findings
HIGH
Publisher changed: jonathanong → jongleberry (on 2015-12-22)
provenance
This version was published by a different npm account than previous versions on 2015-12-22. This could indicate a legitimate maintainer transition or an account compromise.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.