beam
beam
Discover
PulseActivityAnalyticsBest forMapOrgs
Niches
AgentsMCPRAGCoding AssistantsInference & ServingVector DBs
Personal
WatchlistCompareWeekly report
?
Sign in
magic link · no password
LIVE──────── · ──:──:── UTCabout
beam
beam
Discover
PulseActivityAnalyticsBest forMapOrgs
Niches
AgentsMCPRAGCoding AssistantsInference & ServingVector DBs
Personal
WatchlistCompareWeekly report
?
Sign in
magic link · no password
Back to ourmem/omem
[STATUS / DYING]

Is ourmem/omem still actively maintained? (July 2026)

No, not actively. ourmem/omem is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.0/10.

What the signals say
  • Last commit1 months ago (May 24, 2026)
  • Contributors4
  • Stars198 (+0 in last 7 days)
  • Star delta (30d)+2 in last 30 days
  • Velocity score0.0/10 (dying)
What ‘dying’ means on beam

Dying means contributors have dropped, commits have gone silent, or the score has fallen into the bottom decile and is still falling. Beam flags this aggressively because GitHub-star inertia hides decay. Full methodology →

Frequently asked

Is ourmem/omem still actively maintained? (July 2026)

No, not actively. ourmem/omem is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.0/10.

How is beam classifying ourmem/omem?

Beam classifies ourmem/omem as dying with a velocity score of 0.0/10. Beam fuses code activity, package adoption, sentiment, research citation, and production signals into a single 0–10 score; the classification thresholds are explained on /about.

When was the last commit to ourmem/omem?

The most recent commit to ourmem/omem was 1 months ago (May 24, 2026).

How can I track ourmem/omem's status going forward?

Beam refreshes ourmem/omem's velocity score and class daily. The live tool profile is at /tools/1869; the JSON API endpoint is /api/v1/tools/1869.

Full tool profile Methodology API
LIVE──────── · ──:──:── UTCabout