Follow puts Beam Clmm on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.
“Active” by the activity rule's longer window: 2 meaningful events in the last 45 days (the rule needs at least 2); the newest, 2026-09-07, is more than 30 days old.
Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 2 weeks before HEY began reading this project’s sources — not yet read, not zero.
Questions HEY can answer about Beam Clmm — as of 2026-10-19
Is Beam Clmm still being built?
DerivedActive: 0 meaningful events in 30 days; latest ship 42 days ago.Evidence →
What did Beam Clmm ship last?
FactCode changes, week of 2026-09-07 – 2026-09-13 · 6 commits — Code activity, 42 days ago.Evidence →
What does HEY not know about Beam Clmm?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.Details →
Build timeline
Code changes, week of 2026-08-31 – 2026-09-06 · at least 6 commits
This week HEY looked inside 1 of 6 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 1 automated commit (bot accounts or a repeating scripted message) not counted.
Named in code or runs on a hook, read from public code and the chain: a link, never a partnership or an on-chain interaction. A code link is a reference: the code names the token, which shows neither a dependency nor use; only a hook link is a pool running on the other’s hook. As data