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.
Sign up free Scan another repo
134 of your 185 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

chromium/chromium

https://github.com/chromium/chromium · scanned 2026-06-06 00:51 UTC (4 days, 1 hour ago) · 10 languages

177 findings 11/13 scanners ran 60th percentile · Python · medium (20-100K LoC)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

72 actionable findings from 1 signal source. 84 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

Combined
76.4
/100
Security checks
76
72 findings
System graph
—
—% cov · 0 findings
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 41.0 0.20 8.20
documentation_score 88.0 0.15 13.20
practices_score 55.0 0.15 8.25
code_quality 57.0 0.10 5.70
Overall 1.00 69.3
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 0 High 36 Medium 6 Low 10 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 72 System graph 0 Crowd 0 Layer: Quality 64 Security 6 Cicd 1 Software 1

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.

Legacy markers 1 finding
What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.
Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.
How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.
Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.
1 matching finding on this repo
  • high [MINED112] FastAPI PATCH pathlib.Path.home has no auth: Handler `test_remove_le… agents/extensions/install_unittest.py:260
View all legacy markers 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/c904348c-83d7-4c50-b13d-fc58eaf64f97/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c904348c-83d7-4c50-b13d-fc58eaf64f97/

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.