Skip to content

Basestonk Docs

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

Development

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

Build Momentum 16How it is measured

Latest: Code changes, week of 2026-09-21 – 2026-09-27 · 9 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts Basestonk Docs 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 Basestonk Docs

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

View latest ship
Share
More detail
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.
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-09-25, 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 · 9 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 4 commitsCode changes, week of 2026-08-31 – 2026-09-06 · at least 9 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 54d ago.

Building

  • Building activityMeasuredRead 12h 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 3d ago.
  • Published packagesMeasuredRead 3d 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-21 – 2026-09-27 · 9 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.

3 active days in xipzer/basestonk-docs.

This week HEY looked inside 7 of 9 commits to see what changed: 1 changed code, 6 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

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

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: 3 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. 2 code weeks of maintenance or automation only — not counted as building

    Show the 2 weeks
    1. Code changes, week of 2026-10-19 – 2026-10-25 · 1 commit

      Code activitySource-backed

      1 active day in xipzer/basestonk-docs.

      Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.

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

      Code activitySource-backed

      1 active day in xipzer/basestonk-docs.

      Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.

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

    Code activitySource-backed

    3 active days in xipzer/basestonk-docs.

    How HEY read this week

    This week HEY looked inside 2 of 4 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

  3. Code changes, week of 2026-08-31 – 2026-09-06 · at least 9 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    2 active days in Xipzer/basestonk-docs.

    How HEY read this week

    This week HEY looked inside 1 of 9 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

Questions HEY can answer about Basestonk Docs — as of 30 Oct

Show the answers
Is Basestonk Docs still being built?
DerivedActive: 0 counted ships in 30 days; latest ship 35 days ago. Evidence
What did Basestonk Docs ship last?
FactCode changes, week of 2026-09-21 – 2026-09-27 · 9 commits — Code activity, 35 days ago. Evidence
What does HEY not know about Basestonk Docs?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

Sources

1 place HEY reads for Basestonk Docs