@arcgis/charts-components-react
A set of React components that wrap ArcGIS charts components
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Esri org package with clean publisher history; missing gitHead likely reflects a CI environment change, not a supply-chain risk. | ai | |
| phantom-deps | phantom-dep:@arcgis/charts-components | AI (phantom-deps): Same org scope; likely a peer/sibling dep pattern, not a real phantom dep concern for this package. | ai | |
| phantom-deps | phantom-dep:lit | AI (phantom-deps): lit is a transitive/peer dep used by @lit/react wrappers; not directly imported in React wrapper packages by design. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for compiled TS packages. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 5.0.19 | 5 / 0 | |
| 5.0.18 | 5 / 0 | |
| 5.0.17 | 5 / 0 | |
| 5.0.16 | 5 / 0 | |
| 5.0.14 | 5 / 0 | |
| 5.0.10 | 5 / 0 | |
| 5.0.9 | 5 / 0 | |
| 5.0.8 | 5 / 0 | |
| 5.0.7 | 5 / 0 | |
| 5.0.6 | 5 / 0 | |
| 5.0.5 | 5 / 0 | |
| 5.0.4 | 5 / 0 | |
| 5.0.3 | 5 / 0 | |
| 5.0.2 | 5 / 0 | |
| 5.0.1 | 5 / 0 | |
| 5.0.0 | 5 / 0 | |
| 4.34.9 | 5 / 0 | |
| 4.34.8 | 5 / 0 | |
| 4.34.7 | 5 / 0 |
v5.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.14
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dan11669.
This version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.9
2 findingsThis version was published by a different npm account than previous versions on 2025-11-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.