Notebook Share Gate — .ipynb output leak audit

It reads the saved outputs inside a .ipynb file — stream text, text/plain and text/html results, error values and stored tracebacks — plus cell source and notebook metadata. Eighteen rules flag live credentials, customer emails, IBANs, full card numbers, internal hostnames, private addresses, out-of-order execution and saved widget state.

Data scientists and analytics engineers who hand notebooks to other people: attaching an .ipynb to a Jira ticket, pushing it to a shared repo, sending it to a risk or audit team. It is aimed at teams handling customer records in the EU and UK, where a shared output cell is a personal-data disclosure.

Secret scanners and pre-commit hooks read the code in a diff. A notebook keeps what the code printed in a separate JSON output blob, base64 and escaped strings included, and a chatbot cannot read a file you have not pasted into it. This engine walks the notebook structure itself and reports the file line.

Free and keyless: audit the notebook you have open, with every finding named by rule, severity and line number. That job finishes on its own. The licensed layer changes scope and ownership — it sweeps every .ipynb in the workspace in one pass and exports a dated audit record you keep on file.

GDPR Art. 33 gives you 72 hours from becoming aware of a personal-data breach to notify the supervisory authority, and Art. 83(5) caps the administrative fine for this class of infringement at EUR 20 million or 4 % of total worldwide annual turnover, whichever is higher. The extension is $29 once.