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.
Sign up free Scan another repo

verygoodplugins/automem

https://github.com/verygoodplugins/automem · scanned 2026-06-16 00:48 UTC (2 months, 1 week ago)

151 raw signals (0 security + 151 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 122 actionable findings from 1 signal source. 29 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
45.8
/100
Security checks
46
0 findings
System graph
46
100.0% cov · 122 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 23 Medium 9 Low 82 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 122 Crowd 0 Layer: Software 23 Frontend 3 Hardware 5 Security 18 Cicd 3 Quality 29 Api 41
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 45.8/100 with 100.0% coverage. It contains 2046 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 151 findings — concentrated in api (41), quality (38), software (23). Risk profile is high: 0 critical, 23 high, 20 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 114 of 122 actionable findings. 151 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
CLAUDE.md:149 SecretsClaude instruction
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/mcp/sse (mcp-sse-server/test/server.test.js:686)
`mcp-sse-server/test/server.test.js:686` calls `GET http://127.0.0.1:${port}/mcp/sse` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/mcp/sse` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/mcp (mcp-sse-server/test/server.test.js:325)
`mcp-sse-server/test/server.test.js:325` calls `POST http://127.0.0.1:${port}/mcp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/mcp` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/mcp (mcp-sse-server/test/server.test.js:360)
`mcp-sse-server/test/server.test.js:360` calls `POST http://127.0.0.1:${port}/mcp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/mcp` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/mcp (mcp-sse-server/test/server.test.js:491)
`mcp-sse-server/test/server.test.js:491` calls `POST http://127.0.0.1:${port}/mcp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/mcp` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/mcp/ (mcp-sse-server/test/server.test.js:406)
`mcp-sse-server/test/server.test.js:406` calls `POST http://127.0.0.1:${port}/mcp/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/mcp` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/mcp/ (mcp-sse-server/test/server.test.js:447)
`mcp-sse-server/test/server.test.js:447` calls `POST http://127.0.0.1:${port}/mcp/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/mcp` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
high System graph security auth conf 1.00 Flask mutation route `_associate` without `@login_required` — automem/api/memory.py:168
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/memory.py:168 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `_by_tag` without `@login_required` — automem/api/memory.py:160
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/memory.py:160 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `_delete` without `@login_required` — automem/api/memory.py:156
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/memory.py:156 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `_store` without `@login_required` — automem/api/memory.py:148
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/memory.py:148 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `_update` without `@login_required` — automem/api/memory.py:152
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/memory.py:152 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `associate` without `@login_required` — automem/api/memory.py:765
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/memory.py:765 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `by_tag` without `@login_required` — automem/api/memory.py:688
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/memory.py:688 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `consolidate` without `@login_required` — automem/api/consolidation.py:22
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/consolidation.py:22 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `delete` without `@login_required` — automem/api/memory.py:666
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/memory.py:666 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `enrichment_reprocess` without `@login_required` — automem/api/enrichment.py:36
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/enrichment.py:36 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `merge_entity` without `@login_required` — automem/api/entity.py:400
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/entity.py:400 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `reembed` without `@login_required` — automem/api/admin.py:76
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/admin.py:76 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `store_batch` without `@login_required` — automem/api/memory.py:833
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/memory.py:833 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `store` without `@login_required` — automem/api/memory.py:203
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/memory.py:203 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `sync_missing` without `@login_required` — automem/api/admin.py:233
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/admin.py:233 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `update` without `@login_required` — automem/api/memory.py:513
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
automem/api/memory.py:513 securityAuth flask unauth route
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — mcp-sse-server/test/server.test.js:686
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: mcp-sse-server/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 10 occurrences GitHub Action is tag-pinned rather than SHA-pinned
pre-commit/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 10 locations
.github/workflows/docker-build-mcp-automem.yml:52, 56, 64, 82 (4 hits)
.github/workflows/docker-build.yml:54, 58, 66, 82 (4 hits)
.github/workflows/ci.yml:32, 114 (2 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
3 files, 3 locations
.github/workflows/docker-build-mcp-automem.yml
.github/workflows/docker-build.yml
.github/workflows/release-please.yml
CI/CD securitySupply chainGithub actions
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/lab/run_recall_test.py:179
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 27 placeholder/mock markers across 8 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 109 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AUTOMEM_API_URL`, `AUTOMEM_BACKUP_DIR`, `AUTOMEM_ENDPOINT`, `AUTOMEM_MODELS_DIR`, `AUTOMEM_TEST_API_TOKEN`, `AUTOMEM_TEST_BASE_URL`, `AUTOMEM_URL`, `CLASSIFICATION_API_KEY` + 101 more. Add them (with a placeholder/comment) to .env.example so onboa…
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 382 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:18-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
mcp-sse-server/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:2 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 10 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
4 files, 10 locations
.github/workflows/ci.yml:27, 42, 68, 98 (4 hits)
.github/workflows/backup.yml:16, 19 (2 hits)
.github/workflows/docker-build-mcp-automem.yml:49, 94 (2 hits)
.github/workflows/docker-build.yml:51, 94 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 9 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/bench/compare_results.py:load_results, scripts/bench/analyze_locomo_results.py:load_results This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're…
9 occurrences
repo-level (9 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: automem/api/recall.py:startup_recall, automem/api/entity.py:merge_candidates, automem/api/consolidation.py:status This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or docume…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: automem/embedding/openai.py:dimension, automem/embedding/fastembed.py:dimension, automem/embedding/placeholder.py:dimension, automem/embedding/voyage.py:dimension This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see http…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `avg_old` in scripts/rescore_relevance.py:204
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `fix_v1` in scripts/lab/run_recall_test.py:12
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `load_from_backup` in scripts/audit_relevance.py:34
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `restore_from_backup` in scripts/restore_from_backup.py:8
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `restore_from_backup` in tests/test_backup_endpoint.py:14
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `run_backup` in scripts/backup_automem.py:166
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_compute_metadata_score_gate_zero_default_matches_legacy` in tests/test_api_endpoints.py:543
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_prompt_flag_off_is_byte_identical_to_legacy` in tests/benchmarks/longmemeval/test_answer_prompt.py:100
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: analyze_memories
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/analytics/runtime_helpers.py:99
low System graph software Dead code conf 1.00 Possibly dead Python function: connect_loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/automem_watch.py:367
low System graph software Dead code conf 1.00 Possibly dead Python function: consolidate_memories
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/consolidation/runtime_routes.py:96
low System graph software Dead code conf 1.00 Possibly dead Python function: consolidation_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/consolidation/runtime_routes.py:135
low System graph software Dead code conf 1.00 Possibly dead Python function: create_association
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/consolidation/runtime_routes.py:7
low System graph software Dead code conf 1.00 Possibly dead Python function: detect_patterns
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/enrichment/runtime_bindings.py:63
low System graph software Dead code conf 1.00 Possibly dead Python function: detect_patterns
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/enrichment/runtime_helpers.py:74
low System graph software Dead code conf 1.00 Possibly dead Python function: enrichment_worker
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/enrichment/runtime_worker.py:77
low System graph software Dead code conf 1.00 Possibly dead Python function: enrichment_worker
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/enrichment/runtime_queue_bindings.py:66
low System graph software Dead code conf 1.00 Possibly dead Python function: find_temporal_relationships
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/enrichment/runtime_bindings.py:53
low System graph software Dead code conf 1.00 Possibly dead Python function: find_temporal_relationships
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/enrichment/runtime_helpers.py:15
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_placeholder_embedding
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/app_helper_bindings.py:51
low System graph software Dead code conf 1.00 Possibly dead Python function: link_semantic_neighbors
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/enrichment/runtime_bindings.py:74
low System graph software Dead code conf 1.00 Possibly dead Python function: link_semantic_neighbors
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/enrichment/runtime_helpers.py:177
low System graph software Dead code conf 1.00 Possibly dead Python function: normalize_memory_type
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/config.py:203
low System graph software Dead code conf 1.00 Possibly dead Python function: run_consolidation_tick
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/consolidation/runtime_scheduler.py:6
low System graph software Dead code conf 1.00 Possibly dead Python function: run_sync_check
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/sync/runtime_worker.py:50
low System graph software Dead code conf 1.00 Possibly dead Python function: run_sync_check
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/sync/runtime_bindings.py:33
low System graph software Dead code conf 1.00 Possibly dead Python function: startup_recall
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/analytics/runtime_helpers.py:25
low System graph software Dead code conf 1.00 Possibly dead Python function: sync_worker
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/sync/runtime_worker.py:30
low System graph software Dead code conf 1.00 Possibly dead Python function: sync_worker
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/sync/runtime_bindings.py:44
low System graph software Dead code conf 1.00 Possibly dead Python function: temporal_cutoff
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/enrichment/runtime_bindings.py:50
low System graph software Dead code conf 1.00 Possibly dead Python function: temporal_cutoff
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
automem/enrichment/runtime_helpers.py:10
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — mcp-sse-server/server.js:41
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/benchmarks/core_adapter/evaluate.js:196
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Integrity conf 1.00 Stub function `flush` (body is just `pass`/`return`) — automem/backup.py:362
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: ALL /mcp
`mcp-sse-server/server.js` declares `ALL /mcp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /
`automem/api/viewer.py` declares `ANY /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /<path:path>
`automem/api/viewer.py` declares `ANY /<path:path>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin/reembed
`automem/api/admin.py` declares `ANY /admin/reembed` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin/sync
`automem/api/admin.py` declares `ANY /admin/sync` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /analyze
`automem/api/recall.py` declares `ANY /analyze` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /associate
`automem/api/memory.py` declares `ANY /associate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /backup
`automem/api/backup.py` declares `ANY /backup` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /consolidate
`automem/api/consolidation.py` declares `ANY /consolidate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /consolidate/status
`automem/api/consolidation.py` declares `ANY /consolidate/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /enrichment/reprocess
`automem/api/enrichment.py` declares `ANY /enrichment/reprocess` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /enrichment/status
`automem/api/enrichment.py` declares `ANY /enrichment/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /entities
`automem/api/entity.py` declares `ANY /entities` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /entities/audit
`automem/api/entity.py` declares `ANY /entities/audit` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /entities/merge-candidates
`automem/api/entity.py` declares `ANY /entities/merge-candidates` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /entity/<slug>
`automem/api/entity.py` declares `ANY /entity/<slug>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /entity/<slug>/merge
`automem/api/entity.py` declares `ANY /entity/<slug>/merge` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /memories/<memory_id>/related
`automem/api/recall.py` declares `ANY /memories/<memory_id>/related` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /memory
`automem/api/memory.py` declares `ANY /memory` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /memory/<memory_id>
`automem/api/memory.py` declares `ANY /memory/<memory_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /memory/batch
`automem/api/memory.py` declares `ANY /memory/batch` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /memory/by-tag
`automem/api/memory.py` declares `ANY /memory/by-tag` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /neighbors/<memory_id>
`automem/api/graph.py` declares `ANY /neighbors/<memory_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /recall
`automem/api/recall.py` declares `ANY /recall` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /relations
`automem/api/graph.py` declares `ANY /relations` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /snapshot
`automem/api/graph.py` declares `ANY /snapshot` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /startup-recall
`automem/api/recall.py` declares `ANY /startup-recall` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /stats
`automem/api/graph.py` declares `ANY /stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /stream
`automem/api/stream.py` declares `ANY /stream` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /stream/status
`automem/api/stream.py` declares `ANY /stream/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /types
`automem/api/graph.py` declares `ANY /types` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /mcp/sse
`mcp-sse-server/server.js` declares `GET /mcp/sse` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /ready
`mcp-sse-server/server.js` declares `GET /ready` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /alexa
`mcp-sse-server/server.js` declares `POST /alexa` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /mcp/messages
`mcp-sse-server/server.js` declares `POST /mcp/messages` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: automem/api/recall.py (2936 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/benchmarks/test_locomo.py (2318 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_api_endpoints.py (4480 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/7bef365c-23d4-4c18-99a3-08916b3ee539/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/7bef365c-23d4-4c18-99a3-08916b3ee539/

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.