← Home

esri-leaflet

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

patrickarltesri_devgavinrjgravoisjwasilgeo

Keywords

arcgisesriesri leafletgisleaflet pluginmapping

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata url-dep:karma-edgium-launcher AI (npm-metadata): Dev-only test launcher; not included in published files and does not affect consumers. ai
provenance no-provenance AI (provenance): Established Esri package; lack of provenance is consistent across its long publish history. ai

Versions (showing 3 of 3)

Version Deps Published
3.0.19 2 / 31
3.0.18 2 / 31
3.0.17 2 / 31

v3.0.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.