How Zep Python scored a B.

• code

  60/100
  • ✓ Contributors & bus-factor: 6 recent contributors — concentrated
  • ✓ Commit recency: last commit 30d ago
  • ✓ Commit cadence: 6 commits in 90 days
  • ✓ Issue close ratio: 70% of issues closed
  • ✓ Release cadence: 29 releases in 12 months
  • ✓ Stars (log-damped): 208 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 Zep · notable organisation (verified: Org profile shows a Verified badge for www.getzep.com; profile website https://www.getzep.com, display name Zep, description "Build Agents That Recall What Matters.", location United States of America.)

• audits

  Not measured
  • – Third-party scans: not measurable — no registry listings for this tool

• freshness

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

• community

  Not measured
  • – Community: no community signal yet — nobody has recommended it, posted about it, or shared it on Hacker News

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.