Skip to content

stockpilot

StockFi

Is this your project? Claim it →

AI autopilot for tokenized stocks that can only trade inside the rules you sign. Live on Robinhood Chain testnet.

What HEY knows

Development

Last shipped 42 days agoActive: 0 counted ships in 30 days; latest ship 42 days ago. Evidence Source

Build Momentum 0How it is measured

Latest: voice_take

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

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

Sign in to follow stockpilot

No account? Email me stockpilot’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.

More detail
Not yet known
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.
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: 2 counted ships in the last 45 days (the rule needs at least 2); the newest, 2026-10-11, is more than 30 days old.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsvoice_takeCode changes, week of 2026-10-05 – 2026-10-11 · 109 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 counted building from the project's own sources.
Source2 registered sources, 0 of them context only.ReadRecordsvoice_takeCode changes, week of 2026-10-05 – 2026-10-11 · 109 commitssource:44d4809a-2892-4144-be04-622ce633f3e1What 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 8 of the 10 research questions that apply.
8 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 7h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 42d ago.
  • 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 8h ago.

Code and packages

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

Not applicable here: Package advisories, Contract creation, Contract activity, Published source code, 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

voice_take

GitHub releaseSource-backed

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

Release, read from the team’s GitHub · no deployment linked
What it names
The team’s release names it: “voice_take”.
Stage
A release is code the team published; HEY has not observed it deployed unless a link below says so.
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 established: the text HEY holds names none of the project’s contracts. Timing alone never links a release to 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 2026-10-11 00:10 UTC; HEY first knew on 2026-10-11.
Not known
  • HEY does not hold the commit the release was cut from.
  • HEY has not observed a deployment of this change.
  • Not established: the text HEY holds names none of the project’s contracts. Timing alone never links a release to a deployment.

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.

Shared change · Published

stockpilot was published on HEY with its sources recorded.

Builder status: Active.

Observed by HEY on 2026-10-08Source: HEY’s research record

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: 5 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-10-05 – 2026-10-11 · 109 commits

    Code activitySource-backed

    5 active days in ramadan904/stockpilot.

    How HEY read this week

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

Other changes on HEY’s record

4 changes on HEY’s record for stockpilot: 1 release · 1 new Verified Builder or owner proof · 1 new project on HEY · 1 week of code pushed.

All 4 changes for stockpilot →

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

Sources

2 places HEY reads for stockpilot