Skip to content
Signals
deepseek-ai/deepseek-harness adds ~58,389 stars this week — breakout in TypeScriptTrendNexus signalsstorytold/pdfcraft adds ~27,534 stars this week — emerging in RustTrendNexus signalseternity4719/HowToLiveBetter adds ~19,846 stars this week — breakout in HTMLTrendNexus signalsEbony-Vinyl/dsh-our-free-model adds ~19,846 stars this week — emerging in JavaScriptTrendNexus signalsgarrytan/gstack adds ~15,253 stars this week — breakout in TypeScriptTrendNexus signalsGraphify-Labs/graphify adds ~15,133 stars this week — breakout in PythonTrendNexus signalsodysseus-dev/odysseus adds ~12,428 stars this week — breakout in PythonTrendNexus signalsPanniantong/Agent-Reach adds ~12,213 stars this week — breakout in PythonTrendNexus signalsRisk watch: bagisto/bagisto trends cooling with security score 92TrendNexus signalsRisk watch: thedaviddias/Front-End-Checklist trends cooling with security score 82TrendNexus signalsHealthiest in cohort: ultraworkers/claw-code holds PVI 84 — sustainability leaderTrendNexus signals

thedotmack/claude-mem

Breakoutrank #2

Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More

100.3k+3.6k · 7d 8.8k 328est. Apache-2.0TypeScriptpushed 19h ago

Composite

79

conf 65%

Momentum

76

conf 60%

Vitality (PVI)

82

conf 67%

Community

69

conf 60%

Security & maint.

93

conf 85%

Ecosystem influence

74

conf 60%

Opportunity

66

conf 60%

Breakout · 7d

80%

conf 71%

Executive summary

claude-mem is currently classified as breakout with a composite score of 79/100. Momentum (76) and vitality (82) are aligned — growth is backed by sustained maintenance. Estimated 7-day gain of 3,592 stars against a 100.3k-star base. Risk is assessed as low; the interpretable model puts its probability of entering the top trend cohort within 7 days at 80%.

Analyst note

AI-drafted · numbers from tracked data

The relationship between momentum and vitality suggests that a project with high momentum (76/100) may be more attractive to adopt or build on, as it indicates a significant amount of effort and investment has been made. However, the low vitality score (82/100) implies that the project's underlying issues are still present, which could lead to further decline in momentum if not addressed. In this case, adopting or building on the repository at #2 might be a good option for someone looking to capitalize on its momentum, but it is essential to consider whether the current vitality and security-maintenance scores will support long-term success.

Video breakdown

@gptaiclips on YouTube

90-day trajectory

+13.7k · 30d
2026-07-172026-10-14

Score breakdown

Every input, weight and normalized value — nothing hidden. Inputs marked est. are estimated until the full ingestion pipeline lands.

Momentum

Star velocityest.25%99
Star accelerationest.15%56
Fork velocityest.10%91
Contributor growthest.10%91
Issue activity growthest.10%74
PR activity growthest.10%75
External mention velocityest.10%33
Release event impactest.5%86
Trending-rank persistenceest.5%51

Model tn-interpretable-1.0.0 · confidence 60% · coverage 100%

Project Vitality Index

Commit consistency20%97
Release cadenceest.15%79
PR responsivenessest.15%95
Issue responsivenessest.15%56
Contributor diversityest.10%93
Maintainer continuityest.10%85
Documentation qualityest.5%79
Dependency freshnessest.5%53
Security hygieneest.5%70

Model tn-interpretable-1.0.0 · confidence 67% · coverage 100%

Security & maintenance

Release recency25%98
License clarity20%92
Maintenance status25%97
Dependency stalenessest.15%85
Bus factorest.15%87

Model tn-interpretable-1.0.0 · confidence 85% · coverage 100%

Ecosystem influence

Dependent repositoriesest.30%95
Quality-weighted dependentsest.20%70
Documentation citationsest.15%49
Contributor overlapest.15%58
Registry adoptionest.10%54
Topic centralityest.10%100

Model tn-interpretable-1.0.0 · confidence 60% · coverage 92% · missing: packageRegistryAdoption