Skip to content

CURB

StockFi

Is this your project? Claim and verify →

The ticker tells you the exposure. The curb tells you the conditions. A multi-agent intelligence desk for stock tokens on Robinhood Chain.

What HEY knows

Building
Last shipped 36 days agoActive: 0 meaningful events in 30 days; latest ship 36 days ago. Evidence Source

Build Momentum 18How it is measured

Latest change
Derived15 days ago: Code changes, week of 2026-10-12 – 2026-10-18. Not counted as building. Evidence Source

Maintenance only, read from the team’s GitHub · not a new capability

What this change is
What it names
Maintenance only, not a new capability: 0 of 0 commits HEY read were documentation, dependency or maintenance changes, and none changed code.
Stage
Maintenance is not a new capability, and code is not a deployment.
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-10-12; HEY first knew on 2026-10-12.
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.

Follow puts CURB 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 CURB’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's longer window: 3 meaningful events in the last 45 days (the rule needs at least 2); the newest, 2026-09-21, is more than 30 days old.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-21 – 2026-09-27 · 16 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 37 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 45 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.
Source2 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-09-21 – 2026-09-27 · 16 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 37 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 45 commits+1 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

Latest ship

Checked

Code changes, week of 2026-09-21 – 2026-09-27 · 16 commits

Code activitySource linked

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

1 active day in the-curb/curb.

This week HEY looked inside 1 of 16 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 1 automated commit (bot accounts or a repeating scripted message) not counted.

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

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.

Questions HEY can answer about CURB — as of 27 Oct

Is CURB still being built?
DerivedActive: 0 meaningful events in 30 days; latest ship 36 days ago. Evidence
What did CURB ship last?
FactCode changes, week of 2026-09-21 – 2026-09-27 · 16 commits — Code activity, 36 days ago. Evidence
What does HEY not know about CURB?
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs. Details

Build timeline

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

  1. 3 code weeks of maintenance or automation only — not counted as building

    Show the 3 weeks
    1. Code changes, week of 2026-10-12 – 2026-10-18 · 1 commit

      Code activitySource linked

      1 active day in the-curb/curb.

      Automated commits only — not counted as building. 1 automated commit (bot accounts or a repeating scripted message) not counted.

    2. Code changes, week of 2026-10-05 – 2026-10-11 · 1 commit

      Code activitySource linked

      1 active day in the-curb/curb.

      Automated commits only — not counted as building. 1 automated commit (bot accounts or a repeating scripted message) not counted.

    3. Code changes, week of 2026-09-28 – 2026-10-04 · 1 commit

      Code activitySource linked

      1 active day in the-curb/curb.

      Automated commits only — not counted as building. 1 automated commit (bot accounts or a repeating scripted message) not counted.

  2. Code changes, week of 2026-09-14 – 2026-09-20 · at least 37 commits

    Code activitySource linked

    6 active days in the-curb/curb.

    How HEY read this week

    This week HEY looked inside 3 of 36 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. 1 automated commit (bot accounts or a repeating scripted message) not counted.

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

    Code activitySource linked

    3 active days in the-curb/CURB.

    How HEY read this week

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

What changed

6 changes on HEY’s record for CURB: 6 weeks of code pushed.

All 6 changes for CURB →

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 45d ago.

Building

  • Building activityMeasuredRead 15h 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 4d ago.

Code and packages

  • Repository detailsMeasuredRead 7d ago.
  • Published packagesMeasuredRead 7d 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