jupyter-widgets/ipyleaflet#
A Jupyter - Leaflet.js bridge
package · owned by Jupyter Widgets · on GitHub · scanned at commit 612f4eb
Reach#
Packages: ipyleaflet, 203,943 downloads/month, 289 dependents, last published 2025-06-13; jupyter-leaflet, 195,108 downloads/month, 291 dependents, last published 2025-06-13; jupyter-leaflet, 3,352 downloads/month, 1 dependents, last published 2025-06-13
Container images: none
Run by other repositories: none
Live service: none
Security boundary: no
Why these labels: ipyleaflet is a bridge between Jupyter and Leaflet.js, published on PyPI and npm as ‘ipyleaflet’ and ‘jupyter-leaflet’, making it a package for interactive maps. (deepseek-v4-pro)
Security topics#
zizmor: missing. No sign of zizmor.
SECURITY.md: missing. No SECURITY.md, here or in jupyter-widgets/.github.
PyPI attestations: missing. The latest releases of ipyleaflet (2025-06-13) and jupyter-leaflet (2025-06-13) have no attestations.
npm trusted publishing: missing. The latest version of jupyter-leaflet (2025-06-13) did not use trusted publishing.
Supported Python: missing. The latest releases of ipyleaflet (2025-06-13) and jupyter-leaflet (2025-06-13) allow a Python that no longer gets security fixes.
Owner: done. Owned by Jupyter Widgets.
CI and releases#
Workflows: 3, run on issue_comment, pull_request, push
Publishes: nothing
Secrets: none
Actions: 5, 3 by tag, 2 by branch. Third-party, not pinned: mamba-org/setup-micromamba@main
Build requirements: hatch-nodejs-version, hatchling, jupyterlab
Details#
All actions it uses: actions/checkout@v2, actions/upload-artifact@v4, jupyterlab/maintainer-tools@main, jupyterlab/maintainer-tools@v1, mamba-org/setup-micromamba@main
Files: 295: 77 code, 71 notebook, 55 docs, 46 media, 27 config, 10 other, 7 data, 2 web