Interactive challenges for catching the bugs that Copilot, Cursor, and Claude Code sneak into your pull requests.
A junior developer asked a chatbot to write a script that generates a cryptographically secure random identifier. The AI generated the following code, claiming it uses Node.js standard libraries. What is the issue here?
const crypto = require('crypto');
function generateUserSessionId() {
// Generate a random ID using standard crypto module
const rawToken = crypto.generateRandomToken(32);
return rawToken.toString('hex');
}
console.log(generateUserSessionId());Sign in with GitHub to check your answer.
40
Challenges
7
Categories
₹0
Free Forever
Our challenges are divided into seven category patterns commonly produced by generative AI models.
LLMs invent modules, library arguments, or library functions that look real but don't exist.
Incorrect boundaries, index offsets, pagination calculations, or missing edge cases.
OS command injection, SQL injection, path traversal, or leaked credentials directly written into code.
Stale React state closures, asynchronous listener leaks, or parallel request conditions.
N+1 query problems, heavy calculations running on render cycles, or database connection exhaustion.
Silent failure handlers, anti-patterns, typing escapes, or incorrect React prop drilling patterns.
SSR window clashes, library version mismatch configurations, or incorrect peer configurations.