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.

bk-squared/rfx

https://github.com/bk-squared/rfx · scanned 2026-06-17 01:41 UTC (1 month, 1 week ago)

229 raw signals (0 security + 229 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ +4.0 (diff) · 203 actionable findings from 1 signal source. 26 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 · 203 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 12 Low 84 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 203 Crowd 0 Layer: Software 29 Network 2 Security 1 Cicd 2 Quality 169

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

6 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 7 places
low Near-duplicate function bodies in 8 places
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 4 places repo-level
low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

Legacy markers 10 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

10 matching findings on this repo

low Possibly dead Python function: patch_antenna_legacy_api examples/boundary_spec_demo.py:40
low Possibly dead Python function: metasurface_legacy_api examples/boundary_spec_demo.py:67
low Possibly dead Python function: open_box_legacy_api examples/boundary_spec_demo.py:90
low Old/deprecated-named symbol `sim_legacy` in tests/test_boundary_spec_preflight.…
low Old/deprecated-named symbol `out_legacy` in tests/test_update_e_aniso_inv.py:73
low Old/deprecated-named symbol `g_legacy` in tests/test_nonuniform_xy.py:33
low Old/deprecated-named symbol `res_legacy` in tests/test_scan_segmented_checkpoin…
low Old/deprecated-named symbol `quarantined_legacy` in scripts/check_public_docs_m…
low Old/deprecated-named symbol `_save_field_animation_legacy` in rfx/__init__.py:1…
low Old/deprecated-named symbol `_build_spec_from_legacy` in rfx/api/__init__.py:364

View all legacy markers findings →

Commented-out code 107 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 tests/test_physics_integrity.py:98
info Commented-code block (11 lines) in tests/test_lossy.py:95
info Commented-code block (6 lines) in tests/test_stage2_dual_path.py:61
info Commented-code block (5 lines) in tests/test_waveguide_nu_nontrivial.py:402
info Commented-code block (9 lines) in tests/test_subpixel_pec.py:312
info Commented-code block (9 lines) in tests/test_conservation_laws.py:152
info Commented-code block (6 lines) in tests/test_decay_flux_convergence.py:324
info Commented-code block (6 lines) in tests/test_msl_ad_fd_converged.py:113
info Commented-code block (6 lines) in tests/test_waveguide_port_validation_battery.…
info Commented-code block (10 lines) in tests/test_waveguide_nu_flux.py:128
info Commented-code block (7 lines) in tests/test_kottke_pec_limit.py:323
info Commented-code block (6 lines) in tests/test_simulation.py:606

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

info Commented-code block (5 lines) in rfx/auto_config.py:392

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/dfe97360-98b8-41ce-8d0d-befabd7910fb/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/dfe97360-98b8-41ce-8d0d-befabd7910fb/

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.