@esri/solution-web-tool
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:@esri/arcgis-rest-auth | AI (phantom-deps): Same Esri org scope; monorepo pattern where deps are used transitively, not directly imported. | ai | |
| phantom-deps | phantom-dep:@esri/arcgis-rest-portal | AI (phantom-deps): Same Esri org scope; monorepo transitive usage pattern. | ai | |
| phantom-deps | phantom-dep:@esri/arcgis-rest-request | AI (phantom-deps): Same Esri org scope; monorepo transitive usage pattern. | ai | |
| dependencies | unvetted-dep:@esri/solution-common | AI (dependencies): Sibling package in the same Esri solution.js monorepo; dependency is expected and benign across all versions of this package. | ai | |
| dependencies | unvetted-dep:@esri/solution-simple-types | AI (dependencies): Sibling package in the same Esri solution.js monorepo; dependency is expected and benign across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Esri monorepo package; lack of Sigstore provenance is consistent with its publishing history and not a risk signal here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 6.5.1 | 3 / 1 | |
| 6.5.0 | 3 / 1 | |
| 6.3.1 | 3 / 1 | |
| 6.3.0 | 3 / 1 | |
| 6.0.2 | 6 / 1 |
v6.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.