zotero/web-library

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.

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

Scan timing: clone 7.71s · analysis 4.4s · 33.7 MB · GitHub API rate-limit (preflight)

https://github.com/zotero/web-library · scanned 2026-06-05 14:52 UTC (5 days, 4 hours ago) · 10 languages

316 raw signals (68 security + 248 graph) 11/13 scanners ran 91st percentile · Javascript · medium (20-100K LoC) System graph score 75 (higher by 10)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

66.7% cov · 120 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	89.0	0.20	17.80
`documentation_score`	55.0	0.15	8.25
`practices_score`	82.0	0.15	12.30
`code_quality`	80.0	0.10	8.00
Overall		1.00	84.1

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 1 Medium 14 Low 62 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 28 System graph 120 Crowd 0 Layer: Quality 39 Security 6 Cicd 2 Software 53 Api 1 Frontend 47

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 11 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/`.

11 matching findings on this repo

info Commented-code block (6 lines) in test/utils/env-with-fetch.js:8
info Commented-code block (5 lines) in test/playwright/interaction.desktop.test.js:5…
info Commented-code block (5 lines) in test/playwright/remote-library-update.desktop…
info Commented-code block (16 lines) in src/js/common/annotations.js:106
info Commented-code block (6 lines) in src/js/component/focus-trap.jsx:32
info Commented-code block (5 lines) in src/js/component/form/creator-field.jsx:362
info Commented-code block (5 lines) in src/js/component/common/table.jsx:99
info Commented-code block (5 lines) in src/js/component/item/items/table.jsx:354
info Commented-code block (5 lines) in src/js/component/libraries/collection-tree.js…
info Commented-code block (5 lines) in src/js/reducers/libraries/creating.js:13
info Commented-code block (5 lines) in src/js/hooks/use-tracked-settings-key.js:5

View all commented-out code findings →

Config drift 2 findings

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.

2 matching findings on this repo

high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… src/js/actions/cleanup.js:17
low File has no detected symbols: test/config.test.jsx

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/6a9fbbec-f8ee-4107-b3a5-8557627a95cf/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6a9fbbec-f8ee-4107-b3a5-8557627a95cf/

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.