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.

ViktorBarzin/claude-memory-mcp

https://github.com/ViktorBarzin/claude-memory-mcp · scanned 2026-06-16 00:49 UTC (2 months, 1 week ago)

37 raw signals (0 security + 37 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 35 actionable findings from 1 signal source. 2 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 · 35 findings

Severity distribution — click a segment to filter

Active filters: severity: medium × excluding tests × Reset all

Severity: Critical 0 High 0 Medium 6 Low 27 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 35 Crowd 0 Layer: Hardware 1 Frontend 1 Cicd 4 Quality 8 Api 21

Exclude dismissed / FP Exclude test files

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 69.1/100 with 100.0% coverage. It contains 582 nodes across 23 cross-layer flows, written primarily in mixed languages. Engine surfaced 37 findings — concentrated in api (21), quality (10), cicd (4). Risk profile is low: 0 critical, 0 high, 6 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 6 of 35 actionable findings. 37 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.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — openclaw-plugin/index.mjs:35

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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/claude_memory/ui/static/js/api.js:25

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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.json

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/settings.json VerificationClaude instruction

medium System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned

astral-sh/setup-uv@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

.github/workflows/build.yml:25 CI/CD securitySupply chainGithub actions

medium System graph cicd CI/CD security conf 1.00 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.

.github/workflows/release.yml CI/CD securitySupply chainGithub actions

medium System graph cicd CI/CD security conf 1.00 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.

.github/workflows/build.yml CI/CD securitySupply chainGithub actions

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/ae7506f2-ff75-47b7-901f-bd9a3eecd7d0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ae7506f2-ff75-47b7-901f-bd9a3eecd7d0/

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.