Papermark founder Marc Seitz called out a developer named Nico for claiming to have “vibe coded” a data room product — when the code was actually lifted from Papermark’s open-source repository.
The post hit Hacker News and pulled 177 points and 75 comments, mostly focused on a single question: where’s the line between forking an open-source project and pretending you built something from scratch?
The core accusation:
- Nico presented the data room as his own creation, framed under the trendy “vibe coding” label
- The code traces back to Papermark, an open-source document sharing and data room platform
- No attribution was given to the original project or its contributors
The “vibe coding” framing made this worse, not better. Claiming you talked an AI into generating a product sounds impressive — until someone recognizes their own codebase. The Hacker News thread turned into a broader debate about how AI-assisted development makes it easier to obscure where code actually came from. Copy a repo, run it through an LLM for light refactoring, and suddenly it looks “generated.”
NOTE
Papermark is MIT-licensed, so forking it is legally fine. The issue is misrepresenting a fork as original work — especially when using it to build credibility or attract users.
This pattern will repeat. As more developers use AI tools to modify and ship existing codebases, the gap between “I built this” and “I forked this and changed some variable names” gets harder to spot from the outside. Open-source maintainers already struggle with attribution; vibe coding gives bad actors a new cover story.
Papermark’s codebase is public on GitHub, and Seitz’s receipts are in the original post. If you’re shipping anything derived from open-source work, credit the source — the community will find out anyway.