Follow puts Iziedking on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.
Unknown4 gaps: Published packages (not enough yet), Official docs (no source), API description (no source), Official site changes (no source). Packages name its repository, but none is confirmed as the project’s own.
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 Iziedking — as of 2026-10-19
Is Iziedking still being built?
DerivedQuiet: 0 meaningful events in 30 days; latest ship 34 days ago.Evidence →
What did Iziedking ship last?
FactCode changes, week of 2026-09-14 – 2026-09-20 · 6 commits — Code activity, 34 days ago.Evidence →
What does HEY not know about Iziedking?
Unknown4 gaps: Published packages (not enough yet), Official docs (no source), API description (no source), +1 more. Packages name its repository, but none is confirmed as the project’s own.Details →
Build timeline
Code changes, week of 2026-08-31 – 2026-09-06 · at least 2 commitsiziedking/nock-cli
https://github.com/Iziedking/nock-appContext onlyContext only because HEY found this repository by its owner alone and nothing the project controls ties it to the project; it counts once a moderator accepts it, or once the project’s verified owner adds it and a GitHub claim names it, it names the token’s contract, it carries a Robinhood Chain dedication HEY matched to this project, or its homepage is the project’s own site (one the owner did not type in).
HEY keeps these on record as context. None counts toward the activity status or Build Momentum; each says why.
Code activityCode changes, week of 2026-09-21 – 2026-09-272026-09-26Recorded, not counted: it was read from a source HEY holds only as context, and that source says why under Sources.