jupyter-server/jupyter-scheduler#

Run Jupyter notebooks as jobs

package · owned by Jupyter Server · on GitHub · scanned at commit 955883c

Reach#

  • Packages: jupyter-scheduler, 11,580 downloads/month, 5 dependents, last published 2026-08-07; @jupyterlab/scheduler, 132 downloads/month, 0 dependents, last published 2025-05-16

  • Container images: none

  • Run by other repositories: none

  • Live service: none

  • Security boundary: no

  • Why these labels: The repository contains a Python package ‘jupyter_scheduler’ and an NPM package ‘@jupyterlab/scheduler’, with published packages on PyPI and NPM, and CI workflows that publish releases. (deepseek-v4-pro)

Security topics#

  • zizmor: missing. No sign of zizmor.

  • SECURITY.md: done via organization. Uses the SECURITY.md of jupyter-server/.github.

  • PyPI attestations: missing. The latest release of jupyter-scheduler (2026-08-07) has no attestations.

  • npm trusted publishing: missing. The latest version of @jupyterlab/scheduler (2025-05-16) did not use trusted publishing.

  • Supported Python: missing. The latest release of jupyter-scheduler (2026-08-07) allows Python 3.9, which has had no security fixes since 2025-10-31.

  • Owner: done. Owned by Jupyter Server.

CI and releases#

  • Workflows: 8, run on issue_comment, pull_request, push, release, workflow_dispatch

  • Publishes: npm, jupyter_releaser

  • Secrets: APP_PRIVATE_KEY, NPM_TOKEN

  • Actions: 8, 8 by tag

  • Build requirements: hatchling, jupyterlab

Details#

  • All actions it uses: actions/cache@v3, actions/checkout@v4, actions/create-github-app-token@v1, actions/download-artifact@v4, actions/setup-python@v4, actions/upload-artifact@v4, jupyter-server/jupyter_releaser@v2, jupyterlab/maintainer-tools@v1

  • Files: 197: 106 code, 25 config, 22 media, 15 docs, 12 web, 9 other, 7 notebook, 1 data