Skip to content

kabbalahmonster

No narrative yet

Is this your project? Claim and verify →

Python grid trading bot for Robinhood Chain using 0x API

What HEY knows

Building
Shipping consistentlyShipping: 6 meaningful events in 30 days; latest ship today. Evidence Source

Build Momentum 55How it is measured

Latest ship
Code changes this week (since Mon 19 Oct) · 2 commits · · Code activity

Why it matters: One of 6 meaningful events in the last 30 days: building continued, not a one-off.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts kabbalahmonster 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 kabbalahmonster’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
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

HEY can answer 7 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
Shipping.
“Shipping” by the activity rule: 6 meaningful events in the last 30 days, the newest 2026-10-19.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 19 Oct) · 2 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 2 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 14 commits+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.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.
Source6 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 19 Oct) · 2 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 2 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 14 commits+7 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 this week (since Mon 19 Oct) · 2 commitskabbalahmonster/robinhood-grid-bot-py

Code activitySource linked

1 active day in kabbalahmonster/robinhood-grid-bot-py.

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

Record ship:15d836b0… · 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 kabbalahmonster — as of 2026-10-19

Is kabbalahmonster still being built?
DerivedShipping: 6 meaningful events in 30 days; latest ship today. Evidence
What did kabbalahmonster ship last?
FactCode changes this week (since Mon 19 Oct) · 2 commits — Code activity, today. Evidence
What does HEY not know about kabbalahmonster?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record. Details

Build timeline

  1. Code changes this week (since Mon 19 Oct) · 1 commitkabbalahmonster/grid-bot-dashboard

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in kabbalahmonster/grid-bot-dashboard.

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

  2. Code changes, week of 2026-10-12 – 2026-10-18 · 2 commitskabbalahmonster/grid-bot-dashboard

    Code activitySource linked

    2 active days in kabbalahmonster/grid-bot-dashboard.

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

  3. Code changes, week of 2026-10-12 – 2026-10-18 · 9 commitskabbalahmonster/robinhood-grid-bot-py

    Code activitySource linked

    5 active days in kabbalahmonster/robinhood-grid-bot-py.

    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.

  4. Code changes, week of 2026-10-05 – 2026-10-11 · 14 commitskabbalahmonster/robinhood-grid-bot-py

    Code activitySource linked

    5 active days in kabbalahmonster/robinhood-grid-bot-py.

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

  5. Code changes, week of 2026-10-05 – 2026-10-11 · 11 commitskabbalahmonster/grid-bot-dashboard

    Code activitySource linked

    3 active days in kabbalahmonster/grid-bot-dashboard.

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

  6. Code changes, week of 2026-09-28 – 2026-10-04 · 20 commitskabbalahmonster/robinhood-grid-bot-py

    Code activitySource linked

    4 active days in kabbalahmonster/robinhood-grid-bot-py.

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

  7. Code changes, week of 2026-09-28 – 2026-10-04 · 12 commitskabbalahmonster/grid-bot-dashboard

    Code activitySource linked

    2 active days in kabbalahmonster/grid-bot-dashboard.

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

  8. Code changes, week of 2026-09-21 – 2026-09-27 · 15 commitskabbalahmonster/robinhood-grid-bot-py

    Code activitySource linked

    4 active days in kabbalahmonster/robinhood-grid-bot-py.

    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.

  9. Code changes, week of 2026-09-21 – 2026-09-27 · 2 commitskabbalahmonster/grid-bot-dashboard

    Code activitySource linked

    1 active day in kabbalahmonster/grid-bot-dashboard.

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

  10. Code changes, week of 2026-09-14 – 2026-09-20 · at least 22 commitskabbalahmonster/robinhood-grid-bot-py

    Code activitySource linked

    2 active days in kabbalahmonster/robinhood-grid-bot-py.

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

  11. Code changes, week of 2026-09-14 – 2026-09-20 · at least 10 commitskabbalahmonster/grid-bot-dashboard

    Code activitySource linked

    1 active day in kabbalahmonster/grid-bot-dashboard.

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

  12. Code changes, week of 2026-09-07 – 2026-09-13 · at least 60 commitskabbalahmonster/robinhood-grid-bot-py

    Code activitySource linked

    8 active days in kabbalahmonster/robinhood-grid-bot-py.

    This week HEY looked inside 3 of 60 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.

  13. Code changes, week of 2026-09-07 – 2026-09-13 · at least 23 commitskabbalahmonster/grid-bot-dashboard

    Code activitySource linked

    19 active days in kabbalahmonster/grid-bot-dashboard.

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

  14. Code changes, week of 2026-09-07 – 2026-09-13 · 1 commitkabbalahmonster/bonnet--token-hunter

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in kabbalahmonster/bonnet--token-hunter.

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

  15. Code changes, week of 2026-08-31 – 2026-09-06 · at least 108 commitskabbalahmonster/robinhood-grid-bot-py

    Code activitySource linked

    9 active days in kabbalahmonster/robinhood-grid-bot-py.

    This week HEY looked inside 3 of 108 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.

  16. Code changes, week of 2026-08-31 – 2026-09-06 · at least 40 commitskabbalahmonster/grid-bot-dashboard

    Code activitySource linked

    14 active days in kabbalahmonster/grid-bot-dashboard.

    This week HEY looked inside 3 of 40 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.

  17. Code changes, week of 2026-07-13 – 2026-07-19 · at least 6 commitskabbalahmonster/base-trading-bot

    Code activitySource linked

    1 active day in kabbalahmonster/base-trading-bot.

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

  18. Code changes, week of 2026-07-13 – 2026-07-19 · at least 18 commitskabbalahmonster/robinhood-grid-bot

    Code activitySource linked

    1 active day in kabbalahmonster/robinhood-grid-bot.

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

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about kabbalahmonster? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

20 changes on HEY’s record for kabbalahmonster: 1 build pace change · 19 weeks of code pushed.

All 20 changes for kabbalahmonster →

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 7 of the 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 7m 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 6h ago.
  • Published packagesMeasuredRead 6h 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