beam
beam
Discover
PulseActivityAnalyticsBest forMapOrgs
Niches
AgentsMCPRAGCoding AssistantsInference & Serving
Personal
WatchlistCompareWeekly report
?
Sign in
magic link · no password
LIVE──────── · ──:──:── UTCabout
beam
beam
Discover
PulseActivityAnalyticsBest forMapOrgs
Niches
AgentsMCPRAGCoding AssistantsInference & Serving
Personal
WatchlistCompareWeekly report
?
Sign in
magic link · no password
Back to codelibs/fess
[STATUS / NEW]

Is codelibs/fess still actively maintained? (July 2026)

Yes, and it just launched. codelibs/fess appeared on beam July 10, 2026 and is too new to call yet. Current velocity score: 0.0/10.

What the signals say
  • Last committoday (July 10, 2026)
  • Contributors— no data
  • Stars1,116 (+0 in last 7 days)
  • Star delta (30d)— insufficient history
  • Velocity score0.0/10 (new)
What ‘new’ means on beam

New means the repo recently entered beam’s tracked set. Too little history exists to assign a momentum class yet; check back as more snapshots accumulate. Full methodology →

Frequently asked

Is codelibs/fess still actively maintained? (July 2026)

Yes, and it just launched. codelibs/fess appeared on beam July 10, 2026 and is too new to call yet. Current velocity score: 0.0/10.

How is beam classifying codelibs/fess?

Beam classifies codelibs/fess as new 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 codelibs/fess?

The most recent commit to codelibs/fess was today (July 10, 2026).

How can I track codelibs/fess's status going forward?

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

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