How TencentDB Agent Memory scored an A.

• code

  84/100
  • ✓ Contributors & bus-factor: 33 recent contributors
  • ✓ Commit recency: last commit 4d ago
  • ✓ Commit cadence: 66 commits in 90 days
  • ✓ Issue close ratio: 40% of issues closed
  • ✓ Release cadence: 21 releases in 12 months
  • ✓ Stars (log-damped): 29,907 stars (log-damped)
  • – Star authenticity: star-velocity check unavailable — GitHub no longer publishes stargazer timestamps for this repo
  • – Dependent repos: not measurable — no package listing on a registry we can query

• identity

  80/100
  • ✓ Organisation: Built by Tencent · notable organization (verified: Org profile shows a Verified badge for opensource.tencent.com; profile website https://opensource.tencent.com, display name Tencent, location Shenzhen, China. The mapped org tencentcloud shows a Verified badge for cloud.tencent.com (display name Tencent Cloud).)

• audits

  Not measured
  • – Third-party scans: no third-party scan data from listed registries

• freshness

  100/100
  • ✓ Last shipped: last commit 4d ago — standard-churn tools are expected to ship about every 120d

• community

  23/100
  • – Recommends: no recommends from gate-passing builders yet
  • ✓ Hacker News mentions: 1 Hacker News story pointing at this tool
  • – Signal depth: sparse data — this is an early reading from very few data points

Identity and Community did not lower this score. Identity and Community can only ever add. They did not raise the average for TencentDB Agent Memory, so the score shown is the one it would have without them. The components are still listed above, with their real values.

Components that could not be measured are left out of the average entirely, and their weight is redistributed, never scored as zero. Identity and Community are left out the same way when they would not have raised the score. How scores are calculated.