expressjs/express

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.

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

Scan timing: clone 2.76s · analysis 8.11s · 0.7 MB · GitHub API rate-limit (preflight)

https://github.com/expressjs/express · scanned 2026-06-05 08:36 UTC (5 days, 20 hours ago) · 10 languages

332 raw signals (80 security + 252 graph) 61st percentile · Javascript · medium (20-100K LoC) System graph score 65 (higher by 12)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 20 hours ago · v2 · 164 actionable findings from 2 signal sources. 42 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 · 126 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	69.5	0.25	17.38
`testing_score`	87.0	0.20	17.40
`documentation_score`	63.0	0.15	9.45
`practices_score`	84.0	0.15	12.60
`code_quality`	74.8	0.10	7.48
Overall		1.00	77.1

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 9 Medium 11 Low 125 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 38 System graph 126 Crowd 0 Layer: Quality 18 Security 5 Software 72 Frontend 30 Cicd 1 Api 38

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 (5 lines) in examples/web-service/index.js:93
info Commented-code block (5 lines) in examples/error-pages/index.js:79
info Commented-code block (6 lines) in examples/static-files/index.js:15
info Commented-code block (5 lines) in examples/error/index.js:14
info Commented-code block (6 lines) in examples/route-middleware/index.js:11

View all commented-out code 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/85f8264f-a2a1-4cfa-a7bb-94025c9f6b26/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/85f8264f-a2a1-4cfa-a7bb-94025c9f6b26/

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.