earcut
The fastest and smallest JavaScript polygon triangulation library for your WebGL apps
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/earcut.dev.js | AI (source-diff): Browserify bundle generated by prepublish script; standard build output for browser distribution, not obfuscated code. | ai | |
| provenance | no-provenance | AI (provenance): Legacy package predates Sigstore provenance; trusted publisher with long track record. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 3.0.2 | 0 / 5 | |
| 3.0.1 | 0 / 8 | |
| 3.0.0 | 0 / 8 | |
| 2.2.4 | 0 / 10 | |
| 2.2.3 | 0 / 10 | |
| 2.2.2 | 0 / 10 | |
| 2.2.1 | 0 / 10 | |
| 2.2.0 | 0 / 10 | |
| 2.1.5 | 0 / 10 | |
| 2.1.4 | 0 / 10 | |
| 2.1.3 | 0 / 10 | |
| 2.1.2 | 0 / 10 | |
| 2.1.1 | 0 / 10 | |
| 2.1.0 | 0 / 10 | |
| 2.0.8 | 0 / 10 | |
| 2.0.7 | 0 / 10 | |
| 2.0.6 | 0 / 9 | |
| 2.0.5 | 0 / 9 | |
| 2.0.4 | 0 / 9 | |
| 2.0.3 | 0 / 9 | |
| 2.0.2 | 0 / 7 | |
| 2.0.1 | 0 / 7 | |
| 2.0.0 | 0 / 7 | |
| 1.4.2 | 0 / 8 | |
| 1.4.1 | 0 / 8 | |
| 1.4.0 | 0 / 8 | |
| 1.3.0 | 0 / 8 | |
| 1.2.3 | 0 / 8 | |
| 1.2.2 | 0 / 8 | |
| 1.2.1 | 0 / 8 | |
| 1.2.0 | 0 / 8 | |
| 1.1.0 | 0 / 8 | |
| 1.0.6 | 0 / 6 | |
| 1.0.5 | 0 / 5 | |
| 1.0.4 | 0 / 5 | |
| 1.0.3 | 0 / 5 | |
| 1.0.2 | 0 / 5 | |
| 1.0.1 | 0 / 5 | |
| 1.0.0 | 0 / 5 |
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.