Skip to content

narra

Is this your project? Claim it →

Which meta is printing on Pons v2 / Robinhood Chain right now, and is this token in it? Terminal-first, read-only, agent-friendly.

What HEY knows

Building
Quiet for 42 daysQuiet: 0 counted ships in 30 days; latest ship 42 days ago. Evidence Source

Build Momentum 12How it is measured

Follow puts narra 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 narra’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
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.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Quiet.
“Quiet” by the activity rule: 0 counted ships in the last 30 days, the newest 2026-09-17.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · 52 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 30 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Quiet”.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.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · 52 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 30 commitssource:fed68630-2b4a-4951-b731-3c682142017fWhat 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.
Research coverage: HEY can answer 6 of the 10 research questions that apply.
6 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 21h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

  • Repository detailsMeasuredRead 2d ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

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.

Market figures are context only and never change activity status. Methodology

Latest ship

Checked

Code changes, week of 2026-09-14 – 2026-09-20 · 52 commits

Code activitySource-backed

4 active days in bonsaixbt/narra.

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

Record ship:8cf7eda4… · HEY counts it as building; it does not judge the release’s quality.

Code changes, read from the team’s GitHub · not a deployment
What it names
3 of 3 commits HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
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 a release or a deployment: code is not 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 to the week of 2026-09-17; HEY first knew on 2026-09-18. HEY indexed it later, as history.
Not known
  • No source HEY holds names what this change does.
  • HEY has not observed a deployment of this change.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

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: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes, week of 2026-09-07 – 2026-09-13 · at least 30 commits

    Code activitySource-backed

    1 active day in Bonsaixbt/narra.

    How HEY read this week

    This week HEY looked inside 4 of 30 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.

Questions HEY can answer about narra — as of 29 Oct

Show the answers
Is narra still being built?
DerivedQuiet: 0 counted ships in 30 days; latest ship 42 days ago. Evidence
What did narra ship last?
FactCode changes, week of 2026-09-14 – 2026-09-20 · 52 commits — Code activity, 42 days ago. Evidence
What does HEY not know about narra?
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.

Sources

1 place HEY reads for narra