The snippets, ordered obscure → unmistakable

  1. Snippet 1(Generic helper)
  2. Snippet 2(Rule definition)
  3. Snippet 3(Linter dispatch)
  4. Snippet 4(Reporter / fix)
  5. Snippet 5(Config schema (eslint.config.js))
  6. Snippet 6(lib/index.js)

Why this project gives itself away

The give-away. Snippet 1 is generic. Snippet 2 is the canonical rule shape with meta.type, meta.messages, and create(context). Snippet 3's Linter.verify + Traverser is the ESLint runner. Snippet 4's context.report({ messageId, fix(fixer) }) is the fixer API. Snippet 5 is the flat config (eslint.config.js) introduced in v8. Snippet 6 is the OpenJS Foundation copyright + the "Find and fix problems" tagline.

How a Framed puzzle is built

Every Framed project ships exactly six snippets, hand-ordered from deeply obscure to unmistakable. The first snippet must be plausible for a dozen codebases — a generic loop, a small utility, a comment that could appear anywhere. The last snippet carries a project-specific tell: a function name, a code-comment idiom, a file header, a build invocation. Between them sit four snippets that gradually narrow the field. Reading them in order is half the puzzle: a returning Framed player learns to triangulate on indentation conventions, comment voice, naming, and the small-but-distinctive choices that betray a project's era and community.