forkguarddocs

About

A free, open source tool, built after this malware turned up in my own old repos.

On this page
Prodhosh V.S, GitHub profile picture: an illustration of a developer in headphones at a desk

Prodhosh V.S

Full-stack developer and designer in Chennai, India. Built forkguard after PolinRider hid in his own repos.

#Why it exists

It started with emails from Vercel. Production builds were failing on old projects I had not touched in months, all with the same useless message: npm run build exited with 1. I opened postcss.config.mjs in one of them and scrolled right. After export default config; there were hundreds of spaces, then a block of scrambled JavaScript. Git showed nothing. Same author, same date, same message.

Weeks after I first found it, it was back in 35 of my 53 repos. Cleaning that by hand without losing real work took a whole day. forkguard is the tool I wish I had on the first day.

#Writing

#Roadmap

Planned, with no dates. The command line comes first, and these are built on the same rules.

IdeaWhat it would do
GitHub AppConnect your repos once. It scans every push and opens a fix as a pull request. It never writes to your default branch.
VS Code extensionWarns you before you click “Trust” on a cloned folder, which is where this malware strikes.
Web checkerPaste a GitHub link, or pick a local folder and press run. It stays in your browser, and nothing is edited without asking.
MCP serverLets an AI agent call forkguard as a tool instead of reading rules.

#Contributing

git clone https://github.com/PRODHOSH/forkguard
cd forkguard
npm test

To change this documentation, edit the pages in tools/docs/pages/ and run node tools/build-docs.mjs.

#License and credits

Where to next

Edit this page on GitHub View as Markdown

Type to search. Use the arrow keys and Enter.