← Home

esri-leaflet

npm Repository Homepage
8
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, so a manually published version cannot be tied back to a reviewed commit.

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 8 of 8)

Version Deps Published
3.1.0 2 / 28
3.0.19 2 / 31
3.0.18 2 / 31
3.0.17 2 / 31
3.0.16 2 / 31
3.0.15 2 / 28
3.0.14 2 / 28
3.0.13 2 / 28

v3.1.0

1 finding
INFO No provenance attestation provenance

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

v3.0.16

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.15

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.14

2 findings
MEDIUM Publisher changed: gavinr → gr_e (on 2024-12-17, unremoved on npm for 577d) provenance

This version was published by a different npm account (gr_e) than the most recent previously approved version (gavinr) on 2024-12-17. It has since remained available on npm for 577 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.13

2 findings
MEDIUM Publisher changed: gavinr → gr_e (on 2024-10-25, unremoved on npm for 631d) provenance

This version was published by a different npm account (gr_e) than the most recent previously approved version (gavinr) on 2024-10-25. It has since remained available on npm for 631 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.