Skip to content

Robinhood Screener

No known affiliation with Robinhood — HEY holds no evidence of one.The name borrows Robinhood’s brand; a builder HEY verified is not Robinhood.

Integration record: HEY holds no Robinhood Chain evidence for this project (no token, contract or registry listing on the chain), so its ships are recorded here but it is not a Verified Builder.

Is this your project? Claim it →

What HEY knows

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

Build Momentum 19How it is measured

Follow puts Robinhood Screener 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 Robinhood Screener’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: Brand (not verified), Official docs (no source), API description (no source), Official site changes (no source). Its name or ticker uses Robinhood’s brand. HEY holds no evidence that Robinhood is involved with it; it is researched like any other project. It is kept off the homepage, Under the Radar, the featured spots and the Builder Radar until HEY verifies a builder behind it.
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-01.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · at least 3 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 15 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 13 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".
Research coverage: HEY can answer 7 of the 10 research questions that apply.
7 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityMeasuredRead 3h 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 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

Latest ship

Checked

Code changes, week of 2026-09-28 – 2026-10-04 · at least 3 commits

Code activitySource-backed

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

at least 1 active day in yousefjan2007-crypto/robinhood-screener since 2026-10-01; the count stops at the newest 100 commits listed.

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. 1933 automated commits (bot accounts or a repeating scripted message) not counted.

Record ship:e0caf567… · 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-01; HEY first knew on 2026-10-01.
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-21 – 2026-09-27 · at least 100 commits

    Code activitySource-backed

    at least 1 active day in yousefjan2007-crypto/robinhood-screener since 2026-09-24; the count stops at the newest 100 commits listed.

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

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

    Code activitySource-backed

    at least 1 active day in yousefjan2007-crypto/robinhood-screener since 2026-09-20; the count stops at the newest 100 commits listed.

    How HEY read this week

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

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

    Code activitySource-backed

    2 active days in yousefjan2007-crypto/robinhood-screener.

    How HEY read this week

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

Other changes on HEY’s record

5 changes on HEY’s record for Robinhood Screener: 1 verification change · 4 weeks of code pushed.

All 5 changes for Robinhood Screener →

The full change record holds 1 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

Questions HEY can answer about Robinhood Screener — as of 29 Oct

Show the answers
Is Robinhood Screener still being built?
DerivedActive: 1 counted ship in 30 days; latest ship 28 days ago. Evidence
What did Robinhood Screener ship last?
FactCode changes, week of 2026-09-28 – 2026-10-04 · at least 3 commits — Code activity, 28 days ago. Evidence
What does HEY not know about Robinhood Screener?
Unknown4 gaps: Brand (not verified), Official docs (no source), API description (no source), +1 more. Its name or ticker uses Robinhood’s brand. HEY holds no evidence that Robinhood is involved with it; it is researched like any other project. It is kept off the homepage, Under the Radar, the featured spots and the Builder Radar until HEY verifies a builder behind it.

Sources

1 place HEY reads for Robinhood Screener