Synthetic sample report

Repository review with a visible evidence trail.

This example demonstrates the shape of a completed SlopCop report. The repository, code, and findings are illustrative—not customer data or measured results from a real scan.

example/acme-serviceQuick reviewRevision 7b4e2a1Analysis complete

3findings to review

2correctness leads

1performance lead

20 / 20sample checks complete

Code and evidence

Findings to verify

Each entry separates the observed source from the interpretation and proposed next step.

CorrectnessFinding 1 of 3

Session creation ignores the authentication result

src/auth/login.ts

4const valid = await verifyCredentials(username, password);5return database.createSession(username);

Why it needs review: The session is created without checking valid. A failed password verification can therefore reach the success path in this synthetic example.
Suggested next step: Return an authentication failure when valid is false, and add a regression test that proves no session is created.

CorrectnessFinding 2 of 3

Dry-run mode still reaches the destructive operation

src/accounts/delete-account.ts

4if (dryRun) console.log(`Would delete ${username}`);5await database.deleteAccount(username);

Why it needs review: The dry-run branch records intent but does not return. Execution continues to the real deletion call.
Suggested next step: Return after the preview or make the destructive call the explicit non-dry-run branch.

PerformanceFinding 3 of 3

Repository metadata is fetched once per item

src/repositories/summarize.ts

4for (const repository of repositories) {5  summaries.push(await api.fetchMetadata(repository.id));6}

Why it needs review: The loop performs one remote request per repository. This is a review lead: actual impact depends on list size, provider limits, and whether the client batches internally.
Suggested next step: Measure the production path, then use a bounded bulk request or controlled concurrency if repeated latency is material.

Coverage

What the result does—and does not—say.

This synthetic example shows all 20 sample quick-review check families as complete. A real report records incomplete, unavailable, failed, or unselected work separately; those outcomes are not passes.

A clean report does not guarantee defect-free code. Findings are candidates to verify against runtime behavior, intended contracts, and repository context.

Review your own repository.

Start with a public repository URL or connect selected private GitHub repositories.

Start a repository review