No, not actively. nanobrowser/nanobrowser is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.1/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. nanobrowser/nanobrowser is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.1/10.
Beam classifies nanobrowser/nanobrowser as dying with a velocity score of 0.1/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 nanobrowser/nanobrowser was 6 months ago (November 24, 2025).
Beam refreshes nanobrowser/nanobrowser's velocity score and class daily. The live tool profile is at /tools/584; the JSON API endpoint is /api/v1/tools/584.
