@cachemap/core
The Cachemap core module.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/lodash-es | AI (phantom-deps): @types/lodash-es is a type-only companion to lodash-es; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped monorepo package @cachemap/core; name collision with 'cors' is coincidental, not a typosquat. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.3.2 | 11 / 2 | |
| 5.3.1 | 11 / 2 | |
| 5.2.11 | 11 / 2 | |
| 5.2.10 | 11 / 2 | |
| 5.2.9 | 11 / 2 | |
| 5.2.8 | 11 / 2 |
v5.3.2
2 findingsPackage name '@cachemap/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.11
2 findingsPackage name '@cachemap/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.8
2 findingsPackage name '@cachemap/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.