@arcgis/components-build-utils
Collection of common internal build-time patterns and utilities for ArcGIS Maps SDK for JavaScript 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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ora | AI (phantom-deps): Build utility; dependencies used in config/CLI contexts, not direct imports. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): Build utility; dependencies used in config/CLI contexts, not direct imports. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Build utility; dependencies used in config/CLI contexts, not direct imports. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit dependency for TypeScript runtime. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Build utility; dependencies used in config/CLI contexts, not direct imports. | ai | |
| phantom-deps | phantom-dep:split2 | AI (phantom-deps): Build utility; dependencies used in config/CLI contexts, not direct imports. | ai | |
| phantom-deps | phantom-dep:p-limit | AI (phantom-deps): Build utility; dependencies used in config/CLI contexts, not direct imports. | ai | |
| phantom-deps | phantom-dep:fast-glob | AI (phantom-deps): Build utility; dependencies used in config/CLI contexts, not direct imports. | ai | |
| phantom-deps | phantom-dep:fast-xml-parser | AI (phantom-deps): Build utility; dependencies used in config/CLI contexts, not direct imports. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 5.0.19 | 3 / 0 | |
| 5.0.18 | 3 / 0 | |
| 5.0.17 | 3 / 0 | |
| 5.0.16 | 3 / 0 | |
| 5.0.10 | 3 / 0 | |
| 5.0.9 | 3 / 0 | |
| 5.0.8 | 3 / 0 | |
| 5.0.7 | 3 / 0 | |
| 5.0.6 | 3 / 0 | |
| 5.0.5 | 3 / 0 | |
| 5.0.4 | 3 / 0 | |
| 5.0.3 | 3 / 0 | |
| 5.0.2 | 3 / 0 | |
| 5.0.1 | 3 / 0 | |
| 5.0.0 | 3 / 0 | |
| 4.34.9 | 13 / 0 | |
| 4.34.8 | 13 / 0 | |
| 4.34.7 | 13 / 0 | |
| 4.32.16 | 6 / 0 |
v5.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.