No, not actively. elusznik/mcp-server-code-execution-mode is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.0/10.
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 →
No, not actively. elusznik/mcp-server-code-execution-mode is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.0/10.
Beam classifies elusznik/mcp-server-code-execution-mode 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.
The most recent commit to elusznik/mcp-server-code-execution-mode was 6 months ago (December 5, 2025).
Beam refreshes elusznik/mcp-server-code-execution-mode's velocity score and class daily. The live tool profile is at /tools/954; the JSON API endpoint is /api/v1/tools/954.
