AI Slop Is a Commitment Problem
By Håkon Åmdal · May 2026
The Hacker News thread has hundreds of points. The title: "\"AI slop is killing online communities.\" The top comments are almost all correct."
Forums are filling with plausible-sounding content that costs nothing to generate. Stack Overflow is shutting down hot questions faster than ever. Subreddits are adding proof-of-humanity gates. The problem isn't that the content is wrong — it's that you can no longer use effort as a proxy for legitimacy.
That proxy used to work.
Before LLMs, writing a thoughtful comment required something: time, knowledge, the willingness to be judged publicly. The effort was small — maybe five minutes — but it was real and correlated with having something to say. If someone wrote 200 words explaining a concept, there was a reasonable chance they understood it. Effort was a signal.
Now it isn't.
Claude, GPT, Gemini — all can generate 200 plausible words in seconds, with no knowledge, no accountability, no skin in the game. The cost of producing convincing content dropped to zero. The signal broke. Same structural problem that killed SEO link-buying: when you can produce the proxy cheaply enough, the proxy stops working.
Simon Willison put it directly last week: "Claude Code does not have a professional reputation. It can't take accountability for what it's done." He wasn't criticizing LLMs — he was naming a structural fact. Reputation requires behavioral history. Accountability requires stakes. AI has neither. It produces outputs, not commitments.
GitHired launched the same week on Product Hunt with exactly this problem in mind — proof-of-work for job applications. Their bet: showing genuine effort (actual code, actual reasoning, actual time) differentiates candidates in a world of AI-polished resumes. They're right about the problem.
But effort isn't the right frame. Commitment is.
Effort can be automated convincingly enough, given time. Commitment can't — because commitment means sustained behavior with real costs over real time. Multiple people maintaining a codebase for ten years. Paying invoices on time, every month. Showing up in ways that leave a verifiable trail.
This is what we built Commit around. Not effort-as-signal — behavioral commitment as signal.
When we flag an npm package as CRITICAL because one maintainer controls 100 million weekly downloads, we're not running a security audit. We're measuring the absence of commitment. A healthy package has multiple maintainers who've been contributing for years, consistent releases, organizational backing. These signals survive AI exactly because they require the one thing AI can't fake: repeated, costly, verifiable action sustained over time.
The numbers are stark. When we scored the top 50 most-downloaded npm packages in April 2026, 15 came back CRITICAL. Together: 2.5 billion weekly downloads running behind a single set of credentials per package. minimatch (562M downloads/week, 1 maintainer). chalk (413M, 1 maintainer). glob (332M, 1 maintainer). The difference between safe and critical isn't popularity or code quality. It's the depth of human commitment behind the package.
The AI slop problem isn't a content moderation problem. It's a measurement problem. Communities got used to using effort as shorthand for legitimacy. LLMs made that shorthand worthless overnight.
The answer isn't more moderation. It's better measurement — shifting from "did someone write this?" to "does this person have a verifiable history of showing up?"
Commit does this for code. The signals we measure — maintainer depth, release cadence, contributor longevity — don't degrade when AI gets better. They get harder to fake, because they compound over time.
The same logic applies to everything AI slop is breaking. Content trust, community trust, job applications, code quality. In each case, the old proxy is gone. The replacement isn't effort-detection. It's commitment-measurement.
Slop is cheap. Commitment isn't.
Score your dependencies: getcommit.dev/audit
Top comments (0)