typescript-memoize
Memoize decorator for Typescript
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:darryh.ca | AI (email-domain): Long-established publisher (3422 days, 12 approved versions). Unclaimed domain is a hygiene issue, not evidence of compromise. Package has 443k weekly downloads. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is declared as a dependency and used as a runtime polyfill, common pattern for TypeScript packages of this era. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package predating Sigstore provenance; absence of attestation is expected and not a meaningful risk signal for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 0 / 19 | |
| 1.1.0 | 0 / 19 | |
| 1.0.1 | 0 / 19 | |
| 1.0.0 | 0 / 19 | |
| 0.0.4 | 1 / 2 | |
| 0.0.3 | 1 / 2 | |
| 0.0.2 | 1 / 2 | |
| 0.0.1 | 1 / 2 |
v1.1.1
2 findingsMaintainer email '[email protected]' uses domain 'darryh.ca' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsMaintainer email '[email protected]' uses domain 'darryh.ca' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsMaintainer email '[email protected]' uses domain 'darryh.ca' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsMaintainer email '[email protected]' uses domain 'darryh.ca' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
2 findingsMaintainer email '[email protected]' uses domain 'darryh.ca' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
2 findingsMaintainer email '[email protected]' uses domain 'darryh.ca' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
2 findingsMaintainer email '[email protected]' uses domain 'darryh.ca' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
2 findingsMaintainer email '[email protected]' uses domain 'darryh.ca' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.