OneNoteDev/WebClipper

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

22 of your 44 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 3.18s · analysis 11.56s · 1.3 MB · GitHub preflight 426ms

https://github.com/OneNoteDev/WebClipper · scanned 2026-06-05 20:20 UTC (4 days, 13 hours ago) · 10 languages

151 raw signals (41 security + 110 graph) 41st percentile · Typescript · small (2-20K LoC) System graph score 89 (lower by 25)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 13 hours ago · v2 · 82 actionable findings from 2 signal sources. 14 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 51 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	90.5	0.25	22.62
`testing_score`	0.0	0.20	0.00
`documentation_score`	73.0	0.15	10.95
`practices_score`	67.0	0.15	10.05
`code_quality`	77.6	0.10	7.76
Overall		1.00	64.1

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 3 Medium 9 Low 40 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 31 System graph 51 Crowd 0 Layer: Security 3 Quality 28 Software 39 Cicd 6 Api 1 Frontend 5

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 5 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

5 matching findings on this repo

info Commented-code block (6 lines) in src/scripts/renderer.ts:195
info Commented-code block (5 lines) in src/scripts/extensions/regionOverlay.ts:79
info Commented-code block (7 lines) in src/scripts/extensions/contentCaptureInject.t…
info Commented-code block (5 lines) in src/scripts/extensions/webExtensionBase/webEx…
info Commented-code block (5 lines) in src/scripts/communicator/smartValue.ts:86

View all commented-out code findings →

Config drift 1 finding

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

1 matching finding on this repo

high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… src/scripts/contentCapture/oembedExtractor.ts:64

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/f5e2c8ee-635e-4c0a-aea9-638d777f7487/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f5e2c8ee-635e-4c0a-aea9-638d777f7487/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.