TencentDB Agent Memory
TencentDB Agent Memory is a team-level memory hub for AI Agents — turning conversations, docs, and code into four reusable memory assets (Chat Memory, Skill, LLM-Wiki, Code-Graph) that are governed, shared, and equipped across agents and frameworks.
Is TencentDB Agent Memory safe? Promising trust profile, but some evidence still deserves review.
Compare TencentDB Agent Memory
How does it stack up against its Needs review neighbours?
Pick any agent to compare →In detail: TencentDB Agent Memory scores 61.8/100 (Grade C), ranked #638 of 1378 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.5/10; 77% of recent commits are signed; last pushed 2026-10-21. Every point is earned from checkable signals — never paid placement. How scoring works →
How TencentDB Agent Memory could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 4.5 to 9.0lowest checks: CI-Tests 0, CII-Best-Practices 0, Contributors 0 +9.4 → 71.2 B · #1 of 11
- Sign every commit77% signed today +1.1 → 62.9 C · #4 of 11
Chain of custody
Scanners check what the code says. This traces who ships TencentDB Agent Memory and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/TencentCloud/TencentDB-Agent-Memory, NOASSERTION, last pushed 2026-10-21. 77% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.5/10 (scanned Oct 21, 2026). The checks that decide who can get a change released:
- Code Review8
- Branch Protection1
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 1CI-Tests 0CII-Best-Practices 0Code-Review 8Contributors 0Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 9Maintained 10Packaging -1Pinned-Dependencies 0SAST 0Security-Policy 0Signed-Releases -1Token-Permissions 0Vulnerabilities 10 -
Published packages None
No registry package. TencentDB Agent Memory is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of TencentDB Agent Memory.
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues TencentDB Agent Memory’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How TencentDB Agent Memory compares in Needs review
- #3 Obsidian Second Brain 63.5 +1.7
- #4 ASM 61.9 +0.1
- #5 TencentDB Agent Memory 61.8 this agent
- #6 Turbovec 61.6 −0.2
- #7 Hivemind 53.7 −8.1
Bars show each HVTrust score; the tick marks TencentDB Agent Memory’s 61.8.
Where the 61.8 comes from
HVTrust dimensions vs the Needs review average
61.8 / 100 · 100.0% confidenceTencentDB Agent Memory Needs review average (11 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
85.3 / 100Common questions about TencentDB Agent Memory
Does TencentDB Agent Memory publish package provenance?
Does TencentDB Agent Memory have an OpenSSF Scorecard?
Is TencentDB Agent Memory actively maintained?
What license does TencentDB Agent Memory use?
Are TencentDB Agent Memory's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
Compare TencentDB Agent Memory head-to-head
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- code
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain TencentDB Agent Memory?
For maintainers
HVTrust scores TencentDB Agent Memory from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/tencentdb-agent-memory)
<a href="https://hvtracker.net/agents/tencentdb-agent-memory"><img src="https://hvtracker.net/badge/tencentdb-agent-memory.svg" alt="HVTrust"></a>
Other agents in Needs review
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON