ilbers/isar

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.

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)

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

100.0% cov · 320 findings

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

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.

Duplicates & near-duplicates 3 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

3 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 14 places
low Near-duplicate function bodies in 4 places repo-level

View all duplicates & near-duplicates findings →

Commented-out code 54 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 (5 lines) in scripts/lib/wic/ksparser.py:262
info Commented-code block (11 lines) in scripts/lib/wic/plugins/imager/direct.py:578
info Commented-code block (5 lines) in scripts/lib/wic/plugins/source/empty.py:7
info Commented-code block (5 lines) in scripts/pybootchartgui/pybootchartgui/draw.py…
info Commented-code block (6 lines) in scripts/pybootchartgui/pybootchartgui/parsing…
info Commented-code block (9 lines) in meta/scripts/lib/wic/plugins/source/rootfs-u-…
info Commented-code block (8 lines) in meta/lib/oe/utils.py:113
info Commented-code block (5 lines) in meta/lib/oe/sstatesig.py:70
info Commented-code block (6 lines) in meta/lib/oe/path.py:334
info Commented-code block (7 lines) in bitbake/lib/pyinotify.py:606
info Commented-code block (5 lines) in bitbake/lib/ply/yacc.py:34
info Commented-code block (7 lines) in bitbake/lib/bblayers/query.py:67

View all commented-out code findings →

Config drift 5 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.

5 matching findings on this repo

medium Django view `configuration` may be unauthenticated — bitbake/lib/toaster/toaste… bitbake/lib/toaster/toastergui/views.py:843
medium Django view `configvars` may be unauthenticated — bitbake/lib/toaster/toastergu… bitbake/lib/toaster/toastergui/views.py:860
low Unused endpoint: ANY /^build/(?P<build_id>\d+)/configuration$
low Unused endpoint: ANY /^build/(?P<build_id>\d+)/configvars$
low Unused endpoint: ANY /^project/(?P<pid>\d+)/configuration$

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/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.