Skip to content
Menu

stockFlow

Payments

Is this your project? Claim it →

StockFlow — sUSD stablecoin backed by tokenized stocks on Robinhood Chain.

What HEY knows

Building
Last shipped 24 days agoActive: 1 counted ship in 30 days; latest ship 24 days ago. Evidence Source

Build Momentum 27How it is measured

Latest
Code changes, week of 2026-10-05 – 2026-10-11 · 1 commit
FollowCreate alertTerminal previewView latest ship
Share

Follow puts stockFlow 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 stockFlow’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
Unknown1 gap: API description (no source). Its website links no API description.
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 counted ship in the last 30 days, the newest 2026-10-05.
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-28 – 2026-10-04 · 3 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 1 commit+1 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-28 – 2026-10-04 · 3 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 1 commit+4 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.
Research coverage: HEY can answer 9 of the 10 research questions that apply.
9 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

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

Official site

  • Official docsMeasuredRead 2d ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 6d ago.

Code and packages

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

Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)X (opens in a new tab)Sources

Latest ship

Checked

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

Code activitySource-backed

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

What changed, in the repository’s own words:

1 active day in stockflow5/stockflow.

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

Record ship:44d3b9da… · 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
1 of 1 commit 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-10-05; HEY first knew on 2026-10-05.
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.

View evidence ↗ (opens in a new tab)

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-28 – 2026-10-04 · 3 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in stockflow5/stockflow.

    How HEY read this week

    This week HEY looked inside 1 of 3 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-28 – 2026-10-04 · 3 commits (opens in a new tab)

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

    Code activitySource-backed

    What changed, in the repository’s own words:

    5 active days in StockFlow5/stockFlow.

    How HEY read this week

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

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 1 commit (opens in a new tab)

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

    Code activitySource-backed

    What changed, in the repository’s own words:

    4 active days in StockFlow5/stockFlow.

    How HEY read this week

    This week HEY looked inside 1 of 7 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-07 – 2026-09-13 · at least 7 commits (opens in a new tab)

Questions HEY can answer about stockFlow — as of 29 Oct

Show the answers
Is stockFlow still being built?
DerivedActive: 1 counted ship in 30 days; latest ship 24 days ago. Evidence
What did stockFlow ship last?
FactCode changes, week of 2026-10-05 – 2026-10-11 · 1 commit — Code activity, 24 days ago. Evidence
What does HEY not know about stockFlow?
Unknown1 gap: API description (no source). Its website links no API description.

Sources

4 places HEY reads for stockFlow