@flatten-js/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @flatten-js/core is a legitimate 2D geometry library with 7+ years of history; the Levenshtein match to 'cors' is purely coincidental with no impersonation intent. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.6.12 | 1 / 15 | |
| 1.6.11 | 1 / 15 | |
| 1.6.10 | 1 / 15 | |
| 1.6.8 | 1 / 15 | |
| 1.6.6 | 1 / 15 | |
| 1.6.5 | 1 / 15 | |
| 1.6.4 | 1 / 15 | |
| 1.6.3 | 1 / 15 |
v1.6.12
2 findingsPackage name '@flatten-js/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.
v1.6.11
2 findingsPackage name '@flatten-js/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.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.