Removing GSD Due to Security and Trust Concerns

JeredBlu2026-05-26go watch the original →

the gist

The GSD (Get Shit Done) framework creator allegedly abandoned the project following a $500k meme coin rug pull, creating a supply-chain risk for users. You should remove the original packages and migrate to the community-maintained GSD Redux fork.

Security Risks and Project Abandonment

The original GSD framework is no longer considered safe for local development environments. Following reports of a $500k rug pull involving the associated $GSD meme coin, the creator deleted their social media presence and abandoned the repository. Because the framework can execute arbitrary code within agentic coding harnesses like Claude Code or Codex, the potential for malicious supply-chain updates makes the original installation a significant security liability.

Safe Removal and Migration

Because GSD installations vary by version (GSD1 vs. GSD2/Pi) and environment, automated uninstall scripts are unreliable and potentially dangerous. The recommended approach is to use your local AI coding agent to identify and remove files manually.

Identify files: Run the following command to list potential GSD files in your agent directories without deleting anything:

for d in ~/.claude ~/.codex ~/.gemini ~/.config/opencode ~/.agents; do [ -d "$d" ] && find "$d" -maxdepth 3 \( -iname '*gsd*' -o -iname 'get-shit-done' \) -prune -print; done

Remove GSD2/Pi: If you installed the npm package, run npm uninstall -g gsd-pi.
Remove GSD1: Pipe the output from the identification command into your AI agent (e.g., Claude Code) and instruct it to safely delete the identified files and associated slash commands.
Adopt the fork: For continued use, migrate to the community-governed GSD Redux, which has undergone a security audit to ensure it is free from the original creator's influence.