Tencent/TencentDB-Agent-Memory

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.

https://github.com/Tencent/TencentDB-Agent-Memory · scanned 2026-05-15 07:27 UTC (3 weeks ago) · 10 languages

61 findings (14 legacy + 47 scanner) 53rd percentile · Typescript · medium (20-100K LoC) Scanner says 93 (lower by 20)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 3 weeks ago · v1 · 11 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-14-v3

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	94.2	0.25	23.55
`testing_score`	21.0	0.20	4.20
`documentation_score`	97.0	0.15	14.55
`practices_score`	65.0	0.15	9.75
`code_quality`	66.6	0.10	6.66
Overall		1.00	73.7

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 4 Medium 6 Low 1 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 11 9-layer 0 Crowd 0 Layer: Cicd 4 Quality 7

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.

Fragile runtime 7 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

7 matching findings on this repo

medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … hermes-plugin/memory/memory_tencentdb/supervisor.…:220
medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … hermes-plugin/memory/memory_tencentdb/client.py:44
medium [ERR002] Empty Catch Block: Empty catch blocks hide errors. src/utils/clean-context-runner.ts:563
medium [ERR002] Empty Catch Block: Empty catch blocks hide errors. src/core/tdai-core.ts:173
medium [ERR002] Empty Catch Block: Empty catch blocks hide errors. index.ts:735
medium Duplicated implementation block across source files src/core/tools/memory-search.ts:30
medium Duplicated implementation block across source files src/core/record/l1-dedup.ts:176

View all fragile runtime 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/36e88394-2d24-42dd-b2f2-14d53ee23ff2/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/36e88394-2d24-42dd-b2f2-14d53ee23ff2/

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.