@esri/solution-viewer
Simplifies access to @esri/solution.js.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): mtschudi is a named @esri.com contributor in package.json; transition appears legitimate for this Esri-org package. | ai | |
| provenance | no-provenance | AI (provenance): Esri's solution.js packages are published without Sigstore provenance; this is consistent across the entire package family and not a security concern. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 6.6.2 | 2 / 2 | |
| 6.6.1 | 2 / 2 | |
| 6.5.1 | 2 / 2 | |
| 6.5.0 | 2 / 2 | |
| 6.4.0 | 2 / 2 | |
| 6.3.1 | 2 / 2 | |
| 6.3.0 | 2 / 2 | |
| 6.1.8 | 2 / 2 | |
| 6.1.5 | 2 / 2 | |
| 6.1.4 | 2 / 2 | |
| 6.1.3 | 2 / 2 | |
| 6.1.2 | 2 / 2 | |
| 6.1.1 | 2 / 2 | |
| 6.1.0 | 2 / 2 | |
| 6.0.2 | 2 / 2 | |
| 6.0.0 | 2 / 2 |
v6.1.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mtschudi) than the most recent previously approved version (john4818) on 2025-04-21, but mtschudi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.1.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (john4818) than the most recent previously approved version (mtschudi) on 2025-04-07, but john4818 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.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.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.