@arcgis/coding-components-react
A set of React components that wrap ArcGIS coding 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lit | AI (phantom-deps): lit is a known peer/implicit dep for web-component wrappers; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dep for TypeScript-compiled packages; stable false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.0.19 | 5 / 0 | |
| 5.0.18 | 5 / 0 | |
| 5.0.17 | 5 / 0 | |
| 5.0.16 | 5 / 0 | |
| 4.34.9 | 5 / 0 | |
| 4.34.8 | 5 / 0 | |
| 4.34.7 | 5 / 0 | |
| 4.32.16 | 3 / 0 |
v5.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.34.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.34.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.32.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.