← Home

angular-leaflet-directive

1
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

tombatossals

Keywords

angularjsleafletcli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:shady-links-raw-ip AI (semgrep): Raw IPs are hardcoded WMS tile server URLs in example files; not network exfiltration. ai
semgrep semgrep:eval-usage AI (semgrep): eval() converts user-supplied CRS string to Leaflet CRS object; documented mapping library pattern. ai
phantom-deps phantom-dep:angular AI (phantom-deps): angular is a peer/runtime dep for an AngularJS directive; not directly imported in JS but required at runtime. ai
phantom-deps phantom-dep:leaflet AI (phantom-deps): leaflet is a peer/runtime dep; expected to be present in the host app, not directly imported in source. ai

Versions (showing 1 of 1)

Version Deps Published
0.10.0 2 / 31

v0.10.0

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.