Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.
This change
Release, read from the team’s GitHub · no deployment linked›
What it names
The team’s release names it: “v0.8.7”.
Stage
A release is code the team published; HEY has not observed it deployed unless a link below says so.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it 2026-10-08 04:20 UTC; HEY first knew on 2026-10-08.
Not known
HEY does not hold the commit the release was cut from.
HEY has not observed a deployment of this change.
Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.
Follow puts Networks Registry 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: 7 meaningful events in the last 30 days, the newest 2026-10-08.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsv0.8.7v0.8.6v0.8.5+2 moreWhat 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.
Source1 registered source, 0 of them context only.ReadRecordsv0.8.7v0.8.6v0.8.5+3 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology
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: a week before HEY began reading this project’s sources — not yet read, not zero.
Questions HEY can answer about Networks Registry — as of 2026-10-20
Is Networks Registry still being built?
DerivedActive: 7 meaningful events in 30 days; latest ship 12 days ago.Evidence →
What did Networks Registry ship last?
Factv0.8.7 — GitHub release, 12 days ago.Evidence →
What does HEY not know about Networks Registry?
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-10-05 – 2026-10-11 · 1 commit
Code activity · Source linked
1 active day in graphprotocol/networks-registry.
Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only. 2 automated commits (bot accounts or a repeating scripted message) not counted.
Code changes, week of 2026-09-28 – 2026-10-04 · 3 commits
Code activity · Source linked
2 active days in graphprotocol/networks-registry.
Documentation or maintenance only — not counted as building. This week HEY looked inside 3 commits to see what changed: 3 documentation or maintenance only. 4 automated commits (bot accounts or a repeating scripted message) not counted.
This week HEY looked inside 2 of 5 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there. 9 automated commits (bot accounts or a repeating scripted message) not counted.
Code changes, week of 2026-09-14 – 2026-09-20 · at least 9 commits
Code activity · Source linked
2 active days in graphprotocol/networks-registry.
Documentation or maintenance only — not counted as building. This week HEY looked inside 3 commits to see what changed: 3 documentation or maintenance only. 4 automated commits (bot accounts or a repeating scripted message) not counted.
17 active days in graphprotocol/networks-registry.
This week HEY looked inside 2 of 5 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there. 2 automated commits (bot accounts or a repeating scripted message) not counted.
Code changes, week of 2026-08-31 – 2026-09-06 · at least 4 commits
Code activity · Source linked
16 active days in graphprotocol/networks-registry.
Documentation or maintenance only — not counted as building. This week HEY looked inside 4 commits to see what changed: 4 documentation or maintenance only. 7 automated commits (bot accounts or a repeating scripted message) not counted.
