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.

future-agi/future-agi

https://github.com/future-agi/future-agi · scanned 2026-09-18 20:32 UTC (1 month, 1 week ago)

2452 raw signals (0 security + 2452 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v1 · 2433 actionable findings from 1 signal source. 19 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 · 2433 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 45 High 479 Medium 1223 Low 562 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 2433 Crowd 0 Layer: Software 12 Frontend 10 Security 1283 Network 5 Hardware 16 Cicd 5 Quality 636 Dependencies 465 Api 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 2 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.

2 matching findings on this repo

low Near-duplicate function bodies in 2 places
low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

Legacy markers 29 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

low Old/deprecated-named symbol `cs_api_journey_legacy` in frontend/scripts/api-jou…
low Old/deprecated-named symbol `inferPresetForLegacy` in frontend/src/sections/pro…
low Old/deprecated-named symbol `inferPresetForLegacy` in frontend/src/sections/com…
low Old/deprecated-named symbol `inferPresetForLegacy` in frontend/src/sections/tas…
low Old/deprecated-named symbol `fetchNextSimulationEvalPageLegacy` in frontend/src…
low Old/deprecated-named symbol `_buildBlocksFromLegacy` in frontend/src/sections/f…
low Old/deprecated-named symbol `level_or_legacy` in futureagi/model_hub/models/ann…
low Old/deprecated-named symbol `tokenbf_v1` in futureagi/model_hub/services/legacy…
low Old/deprecated-named symbol `credentials_legacy` in futureagi/simulate/models/a…
low Old/deprecated-named symbol `credentials_legacy` in futureagi/simulate/temporal…
low Old/deprecated-named symbol `credentials_legacy` in futureagi/simulate/services…
low Old/deprecated-named symbol `credentials_legacy` in futureagi/simulate/services…

View all legacy markers findings →

Commented-out code 116 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 (10 lines) in frontend/src/utils/utils.js:211 frontend/src/utils/utils.js:211
info Commented-code block (7 lines) in frontend/src/utils/Mixpanel/EventNames.js:319 frontend/src/utils/Mixpanel/EventNames.js:319
info Commented-code block (7 lines) in frontend/src/components/VariableDrawer/Variab… frontend/src/components/VariableDrawer/VariableDr…:289
info Commented-code block (5 lines) in frontend/src/components/DateRangePicker/DateR… frontend/src/components/DateRangePicker/DateRange…:12
info Commented-code block (5 lines) in frontend/src/components/prompt-section/Prompt… frontend/src/components/prompt-section/PromptSect…:245
info Commented-code block (6 lines) in frontend/src/components/websocket/use-socket.… frontend/src/components/websocket/use-socket.jsx:247
info Commented-code block (5 lines) in frontend/src/components/traceDetailDrawer/Bot… frontend/src/components/traceDetailDrawer/BottomA…:62
info Commented-code block (8 lines) in frontend/src/components/traceDetailDrawer/Cus… frontend/src/components/traceDetailDrawer/CustomR…:191
info Commented-code block (8 lines) in frontend/src/components/logo/logo.jsx:18 frontend/src/components/logo/logo.jsx:18
info Commented-code block (8 lines) in frontend/src/components/custom-model-dropdown… frontend/src/components/custom-model-dropdown/Mod…:52
info Commented-code block (11 lines) in frontend/src/components/custom-model-dropdow… frontend/src/components/custom-model-dropdown/Clo…:58
info Commented-code block (6 lines) in frontend/src/components/ConfigureApiKeysModal… frontend/src/components/ConfigureApiKeysModal/Con…:34

View all commented-out code findings →

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

12 matching findings on this repo

medium Insecure pattern 'local_storage_auth_token' in frontend/scripts/api-journeys/br… frontend/scripts/api-journeys/browser/prototype-p…:347
medium Insecure pattern 'local_storage_auth_token' in frontend/scripts/api-journeys/br… frontend/scripts/api-journeys/browser/dataset-syn…:859
low Very large file: frontend/src/sections/common/EvalPicker/EvalPickerConfigFull.j…
low Very large file: frontend/src/sections/gateway/settings/RoutingConfigTab.jsx (1…
low Very large file: agentcc-gateway/internal/config/config.go (1349 lines)
medium Runtime service client appears to use placeholder configuration
info Commented-code block (6 lines) in frontend/src/components/ConfigureApiKeysModal… frontend/src/components/ConfigureApiKeysModal/Con…:34
info Commented-code block (11 lines) in frontend/src/sections/projects/ConfigNavData… frontend/src/sections/projects/ConfigNavData.jsx:96
info Commented-code block (6 lines) in frontend/src/sections/projects/SessionsView/R… frontend/src/sections/projects/SessionsView/Repla…:96
info Commented-code block (9 lines) in frontend/src/sections/develop-detail/Common/E… frontend/src/sections/develop-detail/Common/Evalu…:118
info Commented-code block (5 lines) in frontend/src/layouts/dashboard/config-navigat… frontend/src/layouts/dashboard/config-navigation.…:98
low Old/deprecated-named symbol `config_copy` in futureagi/model_hub/views/eval_run…

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/186af39b-97de-4b72-bad2-f704948600db/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/186af39b-97de-4b72-bad2-f704948600db/

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.