bbartling/open-fdd

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.

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

Scan timing: clone 18.72s · analysis 21.0s · 22.3 MB · GitHub API rate-limit (preflight)

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

579 raw signals (213 security + 366 graph) 61st percentile · Python · medium (20-100K LoC) System graph score 47 (higher by 24)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 152 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	59.0	0.25	14.75
`testing_score`	100.0	0.20	20.00
`documentation_score`	84.0	0.15	12.60
`practices_score`	76.0	0.15	11.40
`code_quality`	33.2	0.10	3.32
Overall		1.00	71.1

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 73 Medium 16 Low 113 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 96 System graph 152 Crowd 0 Layer: Quality 85 Security 45 Software 53 Cicd 6 Network 5 Hardware 4 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 3 places repo-level
low Near-duplicate function bodies in 4 places

View all duplicates & near-duplicates findings →

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

3 matching findings on this repo

high Phantom test coverage: test_startup_public_bind_with_configured_auth_ok tests/workspace_bridge/test_security.py:151
low File has no detected symbols: workspace/dashboard/vite.config.ts
low Unused endpoint: GET /config/bacnet

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/263848d0-b8f2-4c3c-acce-63b1e80054da/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/263848d0-b8f2-4c3c-acce-63b1e80054da/

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.