@arcgis/ai-agents
ArcGIS AI Agents Package
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:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency for TypeScript-compiled packages; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Corporate SDK package under @arcgis scope; sparse README and no keywords are expected for SDK sub-packages. | ai |
Versions (showing 15 of 15)
| 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.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 |
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.