Skip to content
Menu

chiku524

DEX

Is this your project? Claim and verify →

NFT Gallery — collections including Pugs On The Block on Robinhood Chain.

What HEY knows

Building
Last shipped 10 days agoActive: 1 meaningful event in 30 days; latest ship 10 days ago. Evidence Source

Build Momentum 27How it is measured

Latest ship
Code changes, week of 2026-10-05 – 2026-10-11 · 1 commit · · Code activity

Why it matters: First week of code changes after 25 quiet days.

Latest change
Derived4 days ago: 1 meaningful ship this month, 4 the month before. Evidence
FollowCreate alertTerminal previewView latest ship
Share

Follow puts chiku524 on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me chiku524’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Token market · context
No token tracked
Not yet known
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.

HEY can answer 8 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule: 1 meaningful event in the last 30 days, the newest 2026-10-09.
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 · 1 commitCode changes, week of 2026-09-14 – 2026-09-20 · 8 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 28 commits+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.
Source4 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-10-05 – 2026-10-11 · 1 commitCode changes, week of 2026-09-14 – 2026-09-20 · 8 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 28 commits+5 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
LinksWebsiteGitHubSources

Latest ship

Checked

Code changes, week of 2026-10-05 – 2026-10-11 · 1 commitchiku524/nft-gallery

Code activitySource linked

What changed, in the repository’s own words:

1 active day in chiku524/nft-gallery.

This week HEY looked inside 1 commit to see what changed: 1 changed code.

Record ship:daa8ec38… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗

Builder activity

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 chiku524 — as of 2026-10-19

Is chiku524 still being built?
DerivedActive: 1 meaningful event in 30 days; latest ship 10 days ago. Evidence
What did chiku524 ship last?
FactCode changes, week of 2026-10-05 – 2026-10-11 · 1 commit — Code activity, 10 days ago. Evidence
What does HEY not know about chiku524?
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs. Details

Build timeline

  1. Code changes, week of 2026-09-14 – 2026-09-20 · 8 commitschiku524/nft-gallery

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in chiku524/nft-gallery.

    This week HEY looked inside 1 of 8 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · 8 commits (opens in a new tab)

  2. Code changes, week of 2026-09-07 – 2026-09-13 · at least 28 commitschiku524/nft-gallery

    Code activitySource linked

    What changed, in the repository’s own words:

    12 active days in chiku524/nft-gallery.

    This week HEY looked inside 4 of 28 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 28 commits (opens in a new tab)

  3. Code changes, week of 2026-08-31 – 2026-09-06 · at least 61 commitschiku524/nft-gallery

    Code activitySource linked

    What changed, in the repository’s own words:

    10 active days in chiku524/nft-gallery.

    This week HEY looked inside 3 of 61 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.

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 · at least 61 commits (opens in a new tab)

  4. Code changes, week of 2026-08-24 – 2026-08-30 · 10 commitschiku524/hood-agent

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in chiku524/hood-agent.

    This week HEY looked inside 1 of 10 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-08-24 – 2026-08-30 · 10 commits (opens in a new tab)

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about chiku524? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

6 changes on HEY’s record for chiku524: 1 build pace change · 5 weeks of code pushed.

All 6 changes for chiku524 →

The full change record holds 3 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 8 of the 10 research questions that apply.

8 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 38m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 7d ago.

Code and packages

  • Repository detailsMeasuredRead 1d ago.
  • Published packagesMeasuredRead 1d ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources