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.

sdsrss/claude-mem-lite

https://github.com/sdsrss/claude-mem-lite · scanned 2026-06-16 00:05 UTC (2 months, 3 weeks ago)

194 raw signals (16 security + 178 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 177 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 3 Medium 23 Low 21 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 177 Crowd 0 Layer: Quality 167 Frontend 2 Security 13 Cicd 2

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.

Legacy markers 1 finding

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.

1 matching finding on this repo

info Commented-code block (8 lines) in tests/install-legacy-db-backup.test.mjs:1

View all legacy markers findings →

Commented-out code 134 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 schema.mjs:16
info Commented-code block (5 lines) in project-utils.mjs:17
info Commented-code block (5 lines) in memdir.mjs:4
info Commented-code block (5 lines) in nlp.mjs:238
info Commented-code block (8 lines) in hook-handoff.mjs:35
info Commented-code block (16 lines) in secret-scrub.mjs:11
info Commented-code block (6 lines) in hook-precompact.mjs:1
info Commented-code block (5 lines) in hook-optimize.mjs:275
info Commented-code block (6 lines) in hook-llm.mjs:50
info Commented-code block (6 lines) in hook-memory.mjs:22
info Commented-code block (5 lines) in source-files.mjs:1
info Commented-code block (9 lines) in cli.mjs:17

View all commented-out code 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/7bc24ae0-a322-433a-80b6-9bd861011807/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7bc24ae0-a322-433a-80b6-9bd861011807/

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.