No, not actively. lucidrains/alphafold3-pytorch 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. lucidrains/alphafold3-pytorch is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.0/10.
Beam classifies lucidrains/alphafold3-pytorch 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 lucidrains/alphafold3-pytorch was 8 months ago (September 18, 2025).
Beam refreshes lucidrains/alphafold3-pytorch's velocity score and class daily. The live tool profile is at /tools/2188; the JSON API endpoint is /api/v1/tools/2188.
