Jupyter Blog - Rick Wagner

JupyterCon 2025!

2025-03-31T21:24:00+00:00

JupyterCon 2025 will be in San Diego, California, from November 3 to November 6.

We’re excited to host this year’s JupyterCon in sunny San Diego, California, from November 3–6, 2025. From its beginnings as IPython in 2001, Project Jupyter has grown to a global scale platform with millions of *.ipynb files on GitHub (not all of which are named Untitled.ipynb!). The Jupyter ecosystem has transformed data science, scientific research, and education and has shaped the way a generation of developers and scientists develop their workflows.

Quick Links:

About JupyterCon 2025

At JupyterCon 2025, we will bring together data scientists, business analysts, scientists, educators, developers, core Project Jupyter contributors, data visualization specialists, and tool creators in a collegial environment to push at the boundaries of what can be done with the Project Jupyter ecosystem.

The conference begins on Monday, November 3, with technical training tutorials and workshops, followed by two days of keynote talks and breakout sessions, and ending on November 6 with a day of community-led technical sprints. Attendees can expect in-depth training, insightful keynotes, networking, and practical talks that expand our collective knowledge of what the Project Jupyter platform can do. JupyterCon focuses on real-world practices and how to successfully implement interactive computation in your workflow and projects.

We’re seeking proposals for Presentations (Talks), Tutorials, Group Sessions (Workshops, Birds-of-a-Feather, Symposia), and Posters. Topics can include:

Data Science: Proposals that illustrate how Jupyter is used by data science practitioners in industry, government, science, and beyond.
Community: Proposals that demonstrate the Jupyter community, best practices, and tooling. Community practices include how Jupyter is used in a workflow and introspection into the Jupyter community itself, while tooling includes frontends, kernels, extensions, and other tools in the Jupyter ecosystem.
Research and Scientific Discovery: Proposals on how Jupyter is used in specific scientific research fields, such as medical research, astronomy, physics, climate change, meteorology, humanities, social science, and more.
Education: Proposals in this track focus on how to teach and learn using Jupyter in a variety of settings.
Jupyter Infrastructure: Proposals that focus on deploying Jupyter and JupyterHub at scale in industry, government, high-performance computing, science, education, and other settings. Topics include DevOps, scaling services, security concerns, regulation compliance, and more.

Learn more and submit your talk by Sunday, July 13 at 11:59 PM PDT (UTC -7).

Registration

Reserve your pass by 11:59 PM PDT on August 22 for Early Bird.
Standard pricing continues from August 23 to October 3.
Late registration is from October 4 until the first day of JupyterCon.
Student or faculty can register at a discounted academic rate.

Be recognized for your impact on data science, interactive computing, and data visualization by sponsoring JupyterCon 2025. Project Jupyter has been a leader in the open science and interactive computing renaissance, empowering contributions from academia, industry, and government.

As a sponsor, you’ll be investing in a thriving community of open source developers and maintainers committed to innovation. Sponsorships will position your organization at the center of a vibrant, open source ecosystem and enable you to connect directly with hundreds of expert attendees, researchers, engineers, and decision-makers, and actively shape the conversations driving the next era of data science and interactive computing.

For more details on CFP submissions, registration, and sponsorship, visit the JupyterCon Website.

European Commission Funds Jupyter Bug Bounty Program

2023-07-28T19:46:00+00:00

Three Jupyter Subprojects – Jupyter Server, JupyterLab, and JupyterHub –are participating in a bug bounty program sponsored by the European Commission and hosted on the Intigriti platform.

Intigriti is a cybersecurity company that specializes in crowdsourced security services like bug bounty programs, hybrid penetration testing, and hosting live hacking events. The financial support covers bounties from €250 to €5,000 and is part of the European Commission’s Open Source Software Strategy 2020–2023, which:

Promotes the sharing and reuse of software solutions, knowledge and expertise, to deliver better European services that benefit society and lower costs to that society. The Commission commits to increasing its use of open source not only in practical areas such as IT, but also in areas where it can be strategic.

This is a great opportunity for Project Jupyter to reduce the number of potential vulnerabilities in critical Jupyter components and to evaluate our vulnerability handling processes.

Project Jupyter was selected for sponsorship at the end of 2022. After discussions involving several Jupyter Subprojects and other stakeholders, the three Jupyter software components were chosen for inclusion. Representatives from Jupyter Server, JupyterLab, and JupyterHub have committed to validating and responding to submissions for their area. Focusing on a limited number of key Jupyter components was a way to balance the benefits of identifying vulnerabilities against developer obligations to review vulnerability submissions. The Jupyter Security Subproject is contributing to this effort by drafting the bug bounty program details and being a liaison between Intigriti and the other Jupyter Subprojects.

Submissions are triaged by Intigriti, including reproducing potential vulnerabilities and assigning a severity. The triage process ensures that submissions fall within the scope (software components, versions, etc.) defined by the program. Vulnerability severity is based on Intigriti’s contextualized Common Vulnerability Scoring System (CVSS) and assigned a rating of low, medium, high, critical, or exceptional. The severity determines both the bounty and the response time for Project Jupyter to validate a submission. After a submission passes triage, it is sent to Project Jupyter for validation.

Project Jupyter appreciates the financial support from the European Commission and the help by Intigriti representatives to establish the program. Security researchers and others interested in the bug bounty program can view the details on the Intigriti website.

Requiring 2FA for Jupyter GitHub Organizations

2022-07-05T15:00:00+00:00

This requirement and the outlined plan was discussed and agreed upon at the Jupyter Governance meeting on Friday, July 1, 2022.

By October 1, 2022, Project Jupyter aims to require two-factor authentication (2FA) for all GitHub organizations hosting repositories for official Jupyter Subprojects.

Enabling 2FA is the single most important step Jupyter contributors can take to protect their GitHub accounts from bad actors. This benefits the entire Jupyter Community by reducing the chance for malicious code to be slipped into a repository.

Fortunately, most Jupyter GitHub organization members and external collaborators have 2FA enabled, at this time. This process will get us to 100% so we can enable the requirement as a GitHub org setting.

What’s the process?

GitHub Documentation on 2FA

We recommend that all GitHub users secure their account with 2FA, even if you don’t have an organizational role like admin or owner, or write permissions to a Jupyter repository.

Over the next month (by August 1, 2022) contributors to the Jupyter Security Subproject will reach out to owners of each Jupyter GitHub org with a list of their users without 2FA enabled. The list of users will be an intersection across the GitHub orgs so that users aren’t contacted multiple times, and org maintainers are asked to do double work.

From there, the org owners can decide how they want to work within their area of the Community. They may choose to contact the users or ask the Security Subproject to reach out to the users. Or, the users without 2FA may no longer need the access or role they were granted.

At end of August, 2022, we’ll review the list of the remaining accounts without 2FA. (Hopefully none!) If possible, we’ll begin enabling the requirement on our GitHub orgs. The Security Subproject will work with org owners on plans for contacting any remaining users.

At the end of September, 2022, users without 2FA enabled may lose explicit permissions or roles within Jupyter GitHub orgs. This will only impact access to private repositories, commit privileges, or having a role such as owner or admin. Read access to public repositories will remain the same, along with opening issues or pull requests. And once users enable 2FA on their account, any previous permissions or roles can be restored.

What GitHub orgs does this apply to?

All GitHub orgs hosting repositories for official Jupyter Subprojects.