@vertigis/arcgis-extensions
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:xlsx | AI (dependencies): SheetJS CDN distribution; pinned version; known pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Library package with sparse README; not spam — 412 versions and established ecosystem use. | ai | |
| dependencies | unvetted-dep:esri-proj-codes | AI (dependencies): Esri projection codes utility; benign, consistent dep for an ArcGIS extensions package. | ai | |
| npm-metadata | url-dep:xlsx | AI (npm-metadata): SheetJS distributes via cdn.sheetjs.com as their official channel; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:safe-stable-stringify | AI (phantom-deps): safe-stable-stringify is a declared runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:luxon | AI (phantom-deps): luxon is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| dependencies | unvetted-dep:elasticlunr | AI (dependencies): Small, stable search library; no known malicious history, consistent dep across versions. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 53.12.0 | 10 / 50 | |
| 53.11.0 | 10 / 50 | |
| 53.10.0 | 10 / 50 | |
| 53.9.0 | 10 / 50 |
v53.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v53.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.