echarts
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:types/dist/all.d.ts | AI (source-diff): TypeScript .d.ts barrel export with long re-export lines; not obfuscated code. | ai | |
| provenance | publisher-changed | AI (provenance): 100pah is a long-standing Apache/echarts maintainer (2026 days on npm). | ai | |
| dependencies | unvetted-dep:zrender | AI (dependencies): zrender is ECharts' own rendering engine maintained by the same Apache/ECharts team; it is a legitimate, expected dependency for every version of this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Usage is a legacy JSON.parse fallback pattern; JSON.parse is preferred and new Function is only reached in environments without it. Input is GeoJSON source, not arbitrary user input. | ai |
v6.1.0
3 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
Newly 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.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.