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
80 of your 154 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 3.59s · analysis 8.92s · 54.6 MB · GitHub API rate-limit (preflight)

platonai/Browser4

https://github.com/platonai/Browser4 · scanned 2026-06-05 14:32 UTC (5 days, 5 hours ago) · 10 languages

431 raw signals (141 security + 290 graph) 11/13 scanners ran 100th percentile · Kotlin · large (100-500K LoC) System graph score 88 (lower by 2)

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

Complete repo analysis

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

JSON
Combined
84.7
/100
Security checks
82
58 findings
System graph
88
100.0% cov · 120 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 95.0 0.20 19.00
documentation_score 75.0 0.15 11.25
practices_score 96.0 0.15 14.40
code_quality 67.0 0.10 6.70
Overall 1.00 85.4
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 26 Medium 16 Low 92 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 58 System graph 120 Crowd 0 Layer: Quality 60 Security 19 Cicd 12 Software 44 Api 1 Frontend 39 Hardware 3

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
  • low Old/deprecated-named symbol `isBatchingLegacy` in browser4-tests/browser4-tests…
View all legacy markers findings →
Commented-out code 13 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/`.
12 matching findings on this repo
  • info Commented-code block (6 lines) in browser4-tests/browser4-tests-common/src/main…
  • info Commented-code block (6 lines) in browser4-tests/browser4-tests-common/src/main…
  • info Commented-code block (11 lines) in browser4-tests/browser4-tests-common/src/mai…
  • info Commented-code block (5 lines) in browser4-tests/browser4-tests-common/src/main…
  • info Commented-code block (6 lines) in browser4-tests/browser4-tests-common/src/main…
  • info Commented-code block (6 lines) in browser4-tests/browser4-tests-common/src/main…
  • info Commented-code block (6 lines) in browser4-tests/browser4-tests-common/src/main…
  • info Commented-code block (5 lines) in browser4-tests/browser4-tests-common/src/main…
  • info Commented-code block (10 lines) in browser4-tests/browser4-tests-common/src/mai…
  • info Commented-code block (5 lines) in browser4-tests/browser4-tests-common/src/main…
  • info Commented-code block (5 lines) in browser4-agentic/src/main/resources/skills/pd…
  • info Commented-code block (6 lines) in coworker/scripts/workers/count-total-token-us…
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
  • low File has no detected symbols: cli/browser4-cli/jest.config.js
  • low File has no detected symbols: browser4-core/browser4-browser/src/main/resources…
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/cbf6d4c7-1089-41a0-b635-c49b8192e888/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/cbf6d4c7-1089-41a0-b635-c49b8192e888/

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.