Skip to main content

Jupyter Notebook Tracking

A juypterlab extension to record who edited the notebook, when and for how long.

Suitable for Juypterhub deployments, as it looks for JUPYTERHUB_USER.

Tracking data is updated on each notebook save, then stored under the metadata.tracking key in the notebook's JSON:

Example:

    total_edit_time_seconds: 270
    last_edit_by: mary
    editors:
        tom: 120
        mary: 150
    history:
        - bytes: 6796
          edit_time_seconds: 100
          timestamp: "YYYY-MM-DDTHH:mm:ss.nnnZ"
          user: tom
        - bytes: 7980
          edit_time_seconds: 20
          timestamp: "YYYY-MM-DDTHH:mm:ss.nnnZ"
          user: tom
        - bytes: 12900
          edit_time_seconds: 150
          timestamp: "YYYY-MM-DDTHH:mm:ss.nnnZ"
          user: mary

Requirements

  • JupyterLab >= 4.0.0

Install

To install the extension, execute:

pip install jupyter_notebook_tracking

Uninstall

To remove the extension, execute:

pip uninstall jupyter_notebook_tracking

Contributing

Development install

Note: You will need NodeJS to build the extension package.

The jlpm command is JupyterLab's pinned version of yarn that is installed with JupyterLab. You may use yarn or npm in lieu of jlpm below.

# Clone the repo to your local environment
# Change directory to the jupyter_notebook_tracking directory

# Set up a virtual environment and install package in development mode
python -m venv .venv
source .venv/bin/activate
pip install --editable "."

# Link your development version of the extension with JupyterLab
jupyter labextension develop . --overwrite

# Rebuild extension Typescript source after making changes
# IMPORTANT: Unlike the steps above which are performed only once, do this step
# every time you make a change.
jlpm build

You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.

# Watch the source directory in one terminal, automatically rebuilding when needed
jlpm watch
# Run JupyterLab in another terminal
jupyter lab

With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).

By default, the jlpm build command generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:

jupyter lab build --minimize=False

Development uninstall

pip uninstall jupyter_notebook_tracking

In development mode, you will also need to remove the symlink created by jupyter labextension develop command. To find its location, you can run jupyter labextension list to figure out where the labextensions folder is located. Then you can remove the symlink named jupyter_notebook_tracking within that folder.

Packaging the extension

See RELEASE

Metadata

Release files for jupyter-notebook-tracking 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for jupyter-notebook-tracking 0.1.1
File Size Uploaded
jupyter_notebook_tracking-0.1.1.tar.gz 109.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for jupyter-notebook-tracking 0.1.1
File Interpreter ABI Platform
jupyter_notebook_tracking-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 135.6 kB

Release files / jupyter_notebook_tracking-0.1.1.tar.gz

Download URL jupyter_notebook_tracking-0.1.1.tar.gz
Size 109.6 kB
Tags Source
SHA-256 checksum
How to use checksums
9a9b1d618cad2f99aacc54f4d00beb07b58ac2defdcfea7b7b31d7bbcb9919e5
BLAKE2b-256 checksum
How to use checksums
3d898addcc084c09621131d141fa88497791d12cd6f4a31d91b365b5c751822b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Dec 14, 2025.

Transparency log

Release files / jupyter_notebook_tracking-0.1.1-py3-none-any.whl

Download URL jupyter_notebook_tracking-0.1.1-py3-none-any.whl
Size 26.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cd59d7cce232dedce692de180f9614f19ee4d33bbe0bab016de0f592340e7d91
BLAKE2b-256 checksum
How to use checksums
a61ebab442a2d11c69925c91f39f7124bcb45cba7c0d94c165944717ac3e5d1a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Dec 14, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page