Follow puts monvera 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: 1 meaningful event in the last 30 days, the newest 2026-10-09. Not called Resumed: HEY began reading the source of the newest ships after the quiet stretch before them began, so it did not watch that gap.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-05 – 2026-10-11 · 3 commitsCode changes, week of 2026-08-03 – 2026-08-09 · 48 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
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: 3 weeks before HEY began reading this project’s sources — not yet read, not zero.
Questions HEY can answer about monvera — as of 2026-10-19
Is monvera still being built?
DerivedActive: 1 meaningful event in 30 days; latest ship 10 days ago.Evidence →
What did monvera ship last?
FactCode changes, week of 2026-10-05 – 2026-10-11 · 3 commits — Code activity, 10 days ago.Evidence →
What does HEY not know about monvera?
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-03 – 2026-08-09 · 48 commits
This week HEY looked inside 3 of 48 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.