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

Scan timing: clone 3.01s · analysis 8.07s · 10.6 MB · GitHub API rate-limit (preflight)

ilbers/isar

https://github.com/ilbers/isar · scanned 2026-06-05 14:30 UTC (5 days, 5 hours ago) · 10 languages

859 raw signals (175 security + 684 graph) 29th percentile · Python · large (100-500K LoC) System graph score 52 (higher by 17)

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

Complete repo analysis

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

JSON
Combined
53.9
/100
Security checks
56
60 findings
System graph
52
100.0% cov · 320 findings
Critical
5
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 59.8 0.25 14.95
testing_score 92.0 0.20 18.40
documentation_score 100.0 0.15 15.00
practices_score 67.0 0.15 10.05
code_quality 38.7 0.10 3.87
Overall 1.00 68.3
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 5 High 40 Medium 102 Low 164 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 60 System graph 320 Crowd 0 Layer: Quality 199 Security 67 Software 45 Cicd 3 Frontend 9 Hardware 7 Api 50

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in bitbake/lib/toaster/toastergui/views.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in bitbake/lib/toaster/toastergui/views.py:1416; move to env var / secrets manager.
bitbake/lib/toaster/toastergui/views.py:1416
#2
Possible secret in bitbake/lib/toaster/toastergui/views.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in bitbake/lib/toaster/toastergui/views.py:1418; move to env var / secrets manager.
bitbake/lib/toaster/toastergui/views.py:1418
#3
Possible secret in bitbake/lib/toaster/toastergui/views.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in bitbake/lib/toaster/toastergui/views.py:1420; move to env var / secrets manager.
bitbake/lib/toaster/toastergui/views.py:1420
#4
Possible secret in bitbake/lib/toaster/toastergui/views.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in bitbake/lib/toaster/toastergui/views.py:1494; move to env var / secrets manager.
bitbake/lib/toaster/toastergui/views.py:1494
#5
Possible secret in bitbake/lib/toaster/toastergui/views.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in bitbake/lib/toaster/toastergui/views.py:1496; move to env var / secrets manager.
bitbake/lib/toaster/toastergui/views.py:1496
#6
Possible secret in bitbake/lib/toaster/toastergui/views.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in bitbake/lib/toaster/toastergui/views.py:1498; move to env var / secrets manager.
bitbake/lib/toaster/toastergui/views.py:1498
#7
Insecure pattern 'eval_used' in bitbake/lib/ply/yacc.py:1405
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
bitbake/lib/ply/yacc.py:1405
#8
Insecure pattern 'exec_used' in bitbake/lib/ply/yacc.py:1828
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
bitbake/lib/ply/yacc.py:1828
#9
Insecure pattern 'exec_used' in bitbake/lib/ply/lex.py:219
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
bitbake/lib/ply/lex.py:219
#10
Insecure pattern 'eval_used' in bitbake/lib/bb/command.py:752
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
bitbake/lib/bb/command.py:752

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/be4da8ca-e338-4195-92e9-a8bd1035b103/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/be4da8ca-e338-4195-92e9-a8bd1035b103/

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.