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

Scan timing: clone 4.44s · analysis 9.06s · 22.0 MB · GitHub API rate-limit (preflight)

plotly/plotly.R

https://github.com/plotly/plotly.R · scanned 2026-06-05 13:03 UTC (5 days, 9 hours ago) · 10 languages

187 raw signals (57 security + 130 graph) 45th percentile · Javascript · tiny (<2K LoC) System graph score 80 (lower by 20)

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

Complete repo analysis

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

JSON
Combined
72.6
/100
Security checks
65
27 findings
System graph
80
77.8% cov · 59 findings
Critical
3
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 97.0 0.25 24.25
testing_score 0.0 0.20 0.00
documentation_score 72.8 0.15 10.92
practices_score 67.0 0.15 10.05
code_quality 80.0 0.10 8.00
Overall 1.00 59.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 3 High 4 Medium 7 Low 57 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 27 System graph 59 Crowd 0 Layer: Quality 22 Security 3 Software 51 Cicd 6 Api 1 Frontend 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.

Commented-out code 1 finding
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/`.
1 matching finding on this repo
  • info Commented-code block (6 lines) in inst/htmlwidgets/plotly.js:327
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/7ced1cfa-f2e0-435b-8477-d5c86c8cb5d5/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/7ced1cfa-f2e0-435b-8477-d5c86c8cb5d5/

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.