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.

saorsa-labs/fae

https://github.com/saorsa-labs/fae · scanned 2026-06-16 00:05 UTC (2 months, 2 weeks ago)

109 raw signals (0 security + 109 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 83 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

100.0% cov · 83 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 4 Medium 24 Low 43 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 83 Crowd 0 Layer: Software 10 Frontend 1 Security 10 Cicd 3 Quality 48 Api 11

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 →

Legacy markers 13 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.

12 matching findings on this repo

critical Possible secret in legacy/rust-core/src/fae_llm/observability/README.md legacy/rust-core/src/fae_llm/observability/README…:190
critical Possible secret in legacy/rust-core/src/fae_llm/observability/redact.rs legacy/rust-core/src/fae_llm/observability/redact…:89
low Very large file: legacy/rust-core/src/config.rs (2292 lines)
low Very large file: legacy/rust-core/src/host/channel.rs (2197 lines)
low Very large file: legacy/rust-core/src/host/handler.rs (4344 lines)
low Very large file: legacy/rust-core/src/agent/mod.rs (1523 lines)
low Very large file: legacy/rust-core/src/fae_llm/agent/loop_engine.rs (1646 lines)
low Very large file: legacy/rust-core/src/fae_llm/tools/apple/applescript.rs (1379 …
low Very large file: legacy/rust-core/src/memory/jsonl.rs (2923 lines)
low Very large file: legacy/rust-core/src/memory/sqlite.rs (1779 lines)
low Very large file: legacy/rust-core/src/pipeline/coordinator.rs (5192 lines)
low Very large file: legacy/rust-core/src/skills/python_runner.rs (1837 lines)

View all legacy markers findings →

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

7 matching findings on this repo

info Commented-code block (8 lines) in scripts/hf_jobs_merge_peft_adapter.py:2
info Commented-code block (11 lines) in scripts/hf_jobs_train_orpo.py:2
info Commented-code block (11 lines) in scripts/hf_jobs_train_sft.py:2
info Commented-code block (5 lines) in scripts/benchmark_qwen36.py:44
info Commented-code block (6 lines) in native/macos/Fae/Sources/Fae/Resources/Script…
info Commented-code block (5 lines) in native/macos/Fae/Sources/Fae/Resources/Skills…
info Commented-code block (5 lines) in native/macos/Fae/autoresearch/interactive.py:…

View all commented-out code 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

low Very large file: legacy/rust-core/src/config.rs (2292 lines)
high Agent instruction/config may expose a secret: native/macos/Fae/Sources/Fae/Reso… native/macos/Fae/Sources/Fae/Resources/Skills/sec…:76
high Agent instruction/config may expose a secret: native/macos/Fae/Sources/Fae/Reso… native/macos/Fae/Sources/Fae/Resources/Skills/con…:53

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/9719047d-3f02-4b89-8a87-be497b3d52ae/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9719047d-3f02-4b89-8a87-be497b3d52ae/

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.