@particle-academy/react-echarts
React component library wrapping Apache ECharts with typed components for every chart type
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI with SLSA attestation is a standard supply-chain improvement, not a takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): echarts is the core library this package wraps; its addition as a runtime dep is expected and benign. | ai | |
| provenance | no-provenance | AI (provenance): Only 12% of npm packages have provenance; not a disqualifier for this package. | ai | |
| dependencies | unvetted-dep:echarts-gl | AI (dependencies): echarts-gl is the official 3D extension for Apache ECharts; its use here is expected and legitimate. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.1.3 | 2 / 6 | |
| 1.1.2 | 2 / 6 | |
| 1.1.1 | 2 / 6 | |
| 1.1.0 | 2 / 6 | |
| 1.0.3 | 1 / 7 | |
| 1.0.2 | 1 / 7 | |
| 1.0.1 | 0 / 7 | |
| 1.0.0 | 0 / 7 |
v1.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
2 findingsThis version was published by a different npm account than previous versions on 2026-04-14. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.