thedotmack/claude-mem

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.

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

Scan timing: clone 4.18s · analysis 31.84s · 16.5 MB · GitHub API rate-limit (preflight)

https://github.com/thedotmack/claude-mem · scanned 2026-06-05 07:24 UTC (5 days, 22 hours ago) · 10 languages

953 raw signals (197 security + 756 graph) 7th percentile · Typescript · large (100-500K LoC) System graph score 54 (higher by 7)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 22 hours ago · v2 · 489 actionable findings from 2 signal sources. 86 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 · 368 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	0.0	0.25	0.00
`testing_score`	90.0	0.20	18.00
`documentation_score`	84.7	0.15	12.71
`practices_score`	83.0	0.15	12.45
`code_quality`	52.7	0.10	5.27
Overall		1.00	61.2

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 155 Medium 23 Low 200 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 121 System graph 368 Crowd 0 Layer: Quality 159 Security 40 Cicd 9 Software 70 Frontend 66 Hardware 4 Api 141

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 1 finding

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.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places

View all duplicates & near-duplicates findings →

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

3 matching findings on this repo

low Old/deprecated-named symbol `unstable_legacy` in plugin/ui/viewer-bundle.js:8
low Old/deprecated-named symbol `nLegacy` in src/services/integrations/CodexCliInst…
low Old/deprecated-named symbol `idx_memory_sources_legacy` in src/storage/sqlite/s…

View all legacy markers findings →

Commented-out code 76 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 openclaw/src/index.ts:703
info Commented-code block (5 lines) in tests/write-json-file-atomic.test.ts:78
info Commented-code block (5 lines) in tests/env-isolation.test.ts:130
info Commented-code block (5 lines) in tests/shared/timeline-formatting.test.ts:3
info Commented-code block (5 lines) in tests/cli/hook-stream-discipline.test.ts:14
info Commented-code block (5 lines) in tests/cli/hook-io.test.ts:13
info Commented-code block (5 lines) in tests/utils/claude-md-utils.test.ts:6
info Commented-code block (6 lines) in tests/worker/summary-commit-verification.test…
info Commented-code block (5 lines) in tests/worker/poison-respawn.test.ts:4
info Commented-code block (6 lines) in tests/servers/mcp-server-name-safety.test.ts:1
info Commented-code block (5 lines) in tests/hooks/runtime-selector.test.ts:108
info Commented-code block (5 lines) in tests/server/server-beta-service.test.ts:265

View all commented-out code findings →

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

2 matching findings on this repo

low File has no detected symbols: tests/transcripts/config.test.ts
low Old/deprecated-named symbol `name_v2` in tests/cursor-mcp-config.test.ts:212

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/0a45bdbd-e3a2-4313-82f1-ac455e23cce5/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0a45bdbd-e3a2-4313-82f1-ac455e23cce5/

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.