@eeacms/react-chart-editor
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 |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() in minified lib/ output from upstream plotly/react-chart-editor; not a supply-chain risk for this package. | ai | |
| phantom-deps | phantom-dep:raf | AI (phantom-deps): raf is referenced in jest test config (--setupTestFrameworkScriptFile=raf/polyfill), not a phantom dep concern. | ai | |
| phantom-deps | phantom-dep:styled-components | AI (phantom-deps): styled-components is a legitimate runtime dep used by the chart editor UI components. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.47.8 | 23 / 56 | |
| 0.47.7 | 23 / 56 | |
| 0.47.6 | 23 / 56 | |
| 0.47.5 | 24 / 56 | |
| 0.47.4 | 25 / 56 | |
| 0.47.2 | 25 / 56 | |
| 0.47.1 | 25 / 56 |
v0.47.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.