📢 Welcome to GSD-Core — why the fork, what changed, what's next
This repository (open-gsd/gsd-core) is a community-maintained continuation of the work originally published at [gsd-build/get-shit-done`](https://github.com/gsd-build/get-shit-done) by TÂCHES.
Why the fork exists
The upstream repo appears compromised or abandoned. I have no inside information beyond what's publicly visible — I'm stating what I can confirm and what I can't, deliberately, so you can evaluate yourself.
What I can confirm:
- 🔇 No contact with the original maintainer (TÂCHES) since 2026-04-01 (~7 weeks of silence as of this writing).
- 🚫 TÂCHES social accounts appear deleted or unreachable.
- 💸 The
$GSDtoken associated with the project has been publicly linked to a rug-pull. ⚠️ The upstream repo atgsd-build/get-shit-donecontinues to exist, but with the maintainer unreachable.
What I cannot confirm:
- Whether the original maintainer is safe.
- Whether the TÂCHES GitHub account itself is under their control.
- Whether the rug-pull was the maintainer's action, a co-founder exit, or an account takeover.
Absence of news is not evidence either way. That's why this notice exists.
What I did
In a single migration pass on 2026-05-22:
| Count | Status | |
|---|---|---|
| Code: branches mirrored | 394 | ✓ |
| Code: tags mirrored | 229 | ✓ |
| Labels replicated | 84 | ✓ |
| Open milestones replicated | 1 | ✓ |
| Open issues recreated (with link back) | 77 | ✓ |
| Open PRs recreated (with link back) | 17 | ✓ |
| Fork-origin PRs filed as tracking issues | 9 | ✓ |
| Original repo: items closed + locked with redirect | 103 | ✓ |
| Original repo: README banner + auto-close enforcement | live | ✓ |
The original repo now has a top-of-README warning, a redirect on the New Issue picker, and an Actions workflow that auto-closes + locks anything filed there going forward.
What changed (for users)
| Before | After | |
|---|---|---|
| GitHub | gsd-build/get-shit-done |
open-gsd/gsd-core |
| npm (main) | get-shit-done-cc |
get-shit-done-redux |
| npm (sdk) | @gsd-build/sdk |
@gsd-redux/sdk |
| Issue / PR numbers | source numbering | renumbered; each item links back to original via [from gsd-build/get-shit-done#N] |
$GSD token references |
in README badges | removed — the token is a rug-pull, not a project asset |
@gsd_foundation social |
in README badges | removed — accounts gone |
| Discord | in README badges | kept (may still be valid; community-run) |
What did NOT change
- The code itself — every commit, branch, and tag is preserved bit-for-bit.
- The MIT license.
- The contributors — every commit attribution is intact.
CHANGELOG.mdand.changeset/*— historical entries point at original issue/PR numbers on the old repo, since renumbering would silently corrupt those links.
What I want from you
- If you maintain a downstream fork or integration: plan a cut-over to the new npm package names. Old packages won't get updates.
- If you can reach the original maintainer: please do, and CC me on an issue here.
- If you have technical evidence (on-chain, social, infrastructure) that materially changes the picture above, please open an issue here so others can evaluate.
- If you had an open PR against the upstream from your own fork (we couldn't auto-recreate those — branches live in your fork, not ours): see the tracking issues #96–#104 and re-file when you're ready.
- If you want to keep using GSD as a tool: install the new packages and continue. Aside from the package names and the missing
$GSDtoken badge, it's the same project.
What I will do
- Maintain the code here, accept contributions, and continue publishing releases under the new package names.
- Keep this announcement updated if material new information surfaces about the original project, the maintainer, or the
$GSDtoken. - If the original maintainer resurfaces and the upstream repo + npm tokens are demonstrably under safe control, I'll reconsider how to converge — but until that happens, this is the active home.
— trek-e, fork maintainer (not the original author)