LagrangeDev/lagrange-python

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.

42 of your 60 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.48s · analysis 1.81s · 0.2 MB · GitHub preflight 464ms

https://github.com/LagrangeDev/lagrange-python · scanned 2026-06-05 18:26 UTC (4 days, 19 hours ago) · 10 languages

186 raw signals (56 security + 130 graph) 11th percentile · Python · small (2-20K LoC) System graph score 95 (lower by 48)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 49 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	75.0	0.15	11.25
`security_score`	67.6	0.25	16.90
`testing_score`	0.0	0.20	0.00
`documentation_score`	33.0	0.15	4.95
`practices_score`	42.0	0.15	6.30
`code_quality`	79.0	0.10	7.90
Overall		1.00	47.3

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 5 Medium 5 Low 39 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 27 System graph 49 Crowd 0 Layer: Software 32 Quality 34 Security 7 Api 1 Frontend 1 Cicd 1

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

4 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Commented-out code 8 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/`.

8 matching findings on this repo

info Commented-code block (6 lines) in lagrange/client/client.py:463
info Commented-code block (13 lines) in lagrange/client/message/types.py:25
info Commented-code block (10 lines) in lagrange/client/message/encoder.py:145
info Commented-code block (13 lines) in lagrange/client/message/decoder.py:255
info Commented-code block (8 lines) in lagrange/client/highway/highway.py:378
info Commented-code block (31 lines) in lagrange/client/highway/encoders.py:257
info Commented-code block (6 lines) in lagrange/pb/status/group.py:149
info Commented-code block (5 lines) in lagrange/pb/service/group.py:206

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

medium No CI/CD configuration found

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/35d3b381-1b85-4e26-8074-d09fb3338809/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/35d3b381-1b85-4e26-8074-d09fb3338809/

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.