AI Slop Code Risk Monitor

jupyter/notebook

Name: jupyter/notebook — Jupyter Notebook Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Jupyter Interactive Notebook

2.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for jupyter/notebook, a Jupyter Notebook project with 13,459 GitHub stars. SynthScan examined 23,049 lines of code across 241 source files, recording 35 pattern matches distributed across 8 syntactic categories. The legacy adjusted pattern signal is 2.0 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

2.0

Adjusted Signal

2.0

Raw Pattern Score

100%

Time Factor

2026-10-30

Last Push

13.5K

Stars

Jupyter Notebook

Language

23.0K

Lines of Code

241

Files

Pattern Hits

2026-10-31

Scan Date

0.00

HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 6.3/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 24 finding(s).

Hallucinated Dependency & Supply Chain Risk 1.7/100 · LOW

Are imports declared and package/API names verified? 8 finding(s).

Agent Over-Engineering Ratio 4.2/100 · LOW

Are wrappers, guards, and repeated structures necessary? 16 finding(s).

PR Review Velocity Impact 9.5/100 · LOW

Which changes need focused human review? 35 finding(s).

What These Metrics Mean

Adjusted Signal: Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score: Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor: A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits: Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate: High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files: Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 1MEDIUM 3LOW 31

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 35 distinct pattern matches across 8 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Hyper-Verbose Identifiers13 hits · 13 pts

Severity	File	Line	Snippet	Context
LOW	app/index.template.js	252	async function loadDeferredDisabledFederatedPlugins() {	CODE
LOW	tests/test_app.py	23	def test_notebook_app_flags_are_isolated():	CODE
LOW	tests/test_app.py	31	def test_notebook_app_flags_reach_serverapp():	CODE
LOW	buildutils/src/utils.ts	52	function normalizeDependencySpecifier(	CODE
LOW	buildutils/src/get-latest-lab-version.ts	11	function extractVersionFromReleases(	CODE
LOW	buildutils/src/get-latest-lab-version.ts	37	function extractCurrentJupyterLabVersion(): string {	CODE
LOW	packages/application-extension/src/settingconnector.ts	102	function hideSyntaxHighlightingMenu(	CODE
LOW⚡	notebook/__init__.py	8	def _jupyter_server_extension_paths() -> list[dict[str, str]]:	CODE
LOW⚡	notebook/__init__.py	12	def _jupyter_server_extension_points() -> list[dict[str, Any]]:	CODE
LOW⚡	notebook/__init__.py	19	def _jupyter_labextension_paths() -> list[dict[str, str]]:	CODE
LOW	notebook/app.py	291	def _default_app_settings_dir(self) -> str:	STRING
LOW	notebook/app.py	303	def _default_user_settings_dir(self) -> str:	STRING
LOW	notebook/app.py	314	def server_extension_is_enabled(self, extension: str) -> bool:	STRING

Self-Referential Comments3 hits · 9 pts

Severity	File	Line	Snippet	Context
MEDIUM	tests/conftest.py	56	# Create the index file.	COMMENT
MEDIUM	tests/conftest.py	97	# Create the federated extensions	COMMENT
MEDIUM	docs/source/conf.py	4	# This file is execfile()d with the current directory set to its	COMMENT

Over-Commented Block8 hits · 8 pts

Severity	File	Line	Snippet	Context
LOW	docs/source/conf.py	1	# Jupyter Notebook documentation build configuration file, created by	COMMENT
LOW	docs/source/conf.py	101	# ghissue config	COMMENT
LOW	docs/source/conf.py	141	# If true, '()' will be appended to :func: etc. cross-reference text.	COMMENT
LOW	docs/source/conf.py	221	# "<project> v<release> documentation".	COMMENT
LOW	docs/source/conf.py	241	# since it is needed to properly generate _static in the build directory	COMMENT
LOW	docs/source/conf.py	261	# template names.	COMMENT
LOW	docs/source/conf.py	281		COMMENT
LOW	docs/source/conf.py	341	# latex_show_urls = False	COMMENT

Unused Imports5 hits · 5 pts

Severity	File	Line	Context
LOW	docs/source/conf.py	74	CODE
LOW	notebook/__init__.py	1	CODE
LOW	notebook/__init__.py	5	CODE
LOW	notebook/__init__.py	5	CODE
LOW	notebook/app.py	3	CODE

Empty Error Handlers1 hit · 5 pts

Severity	File	Line	Snippet	Context
HIGH	docs/source/conf.py	77	except ImportError:	CODE

Fake / Example Data3 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	packages/tree-extension/src/fileactions.tsx	36	<div key={'placeholder'}>	CODE
LOW	packages/tree-extension/src/fileactions.tsx	41	this._widgets.set('placeholder', placeholder);	CODE
LOW	packages/tree-extension/src/fileactions.tsx	80	this._widgets.get('placeholder')?.setHidden(selection);	CODE

Modern Structural Boilerplate1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	docs/source/conf.py	18	logger = logging.getLogger(__name__)	CODE

Excessive Try-Catch Wrapping1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	notebook/app.py	84	except Exception:	CODE