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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Named in code or runs on a hook, read from public code and the chain: a link, never a partnership or an on-chain interaction. A code link is a reference: the code names the token, which shows neither a dependency nor use; only a hook link is a pool running on the other’s hook. As data