@esri/solution-web-experience
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-service-admin | AI (phantom-deps): Monorepo peer/transitive dep pattern; same org scope, not a real phantom. | ai | |
| phantom-deps | phantom-dep:@esri/arcgis-rest-portal | AI (phantom-deps): Monorepo peer/transitive dep pattern; same org scope, not a real phantom. | ai | |
| phantom-deps | phantom-dep:@esri/arcgis-rest-request | AI (phantom-deps): Monorepo peer/transitive dep pattern; same org scope, not a real phantom. | ai | |
| phantom-deps | phantom-dep:@esri/arcgis-rest-feature-layer | AI (phantom-deps): Monorepo peer/transitive dep pattern; same org scope, not a real phantom. | ai | |
| phantom-deps | phantom-dep:@esri/arcgis-rest-auth | AI (phantom-deps): Monorepo peer/transitive dep pattern; same org scope, not a real phantom. | ai | |
| dependencies | unvetted-dep:@esri/solution-common | AI (dependencies): First-party Esri package from the same solution.js monorepo; expected sibling dependency. Not a risk signal. | ai | |
| provenance | no-provenance | AI (provenance): Established Esri org package with 565 versions; lack of Sigstore provenance is common and not a risk indicator here. | ai | |
| dependencies | unvetted-dep:@esri/hub-common | AI (dependencies): First-party Esri package; expected dependency for this Esri solution.js ecosystem package. Not a risk signal. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 6.5.1 | 3 / 1 | |
| 6.5.0 | 3 / 1 | |
| 6.4.0 | 3 / 1 | |
| 6.3.0 | 3 / 1 | |
| 6.0.2 | 8 / 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.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.