Roadmap

Work on jetlint is organized into eight category Milestones — one per rule category in the taxonomy. Each Milestone collects the open issues for rules, infra, and documentation that belong to that category. Open Milestones never “complete” the way release Milestones do; they accumulate scope as new upstream rules are identified, and the progress bar reflects what has shipped versus what is still queued.

Click any Milestone to see its open and closed issues, current progress, and any rules waiting for upstream work or new infrastructure.

Active categories

correctness

Code that is wrong: runtime bugs, undefined behavior, type holes. No legitimate reason to write. The largest category, and the one users expect to “just be on” — the recommended preset is drawn entirely from correctness.

suspicious

Code that smells. Usually wrong, occasionally intentional. The author should justify or fix. Default severity is warn.

security

Patterns enabling injection, eval, prototype pollution, or unsafe deserialization. Currently one rule (no-implied-eval); expansion tracks new upstream rules as they appear.

performance

Known-slow patterns with a faster equivalent. No correctness impact.

complexity

Needless complication with a simpler equivalent. No correctness or performance impact.

style

Formatting, naming, ordering. Pure preference; team-configurable. Ships off by default.

a11y

JSX accessibility rules. Blocked on JSX support landing in jetlint — the Milestone exists so the work is visible, but no rules will ship here until the underlying support is in place.

nursery

Rules whose category placement biome hasn’t finalized upstream. Mirrored here so a planned rule has a home; each rule promotes out to its semantic category when biome resolves placement. Distinct from jetlint’s Stability: nursery flag, which marks rules whose behavior is still iterating.

Not tracked here

• Releases. Cut on schedule against the categories above; not themed Milestones in their own right.
• Stability-nursery rules (rules whose behavior is still iterating) live in their semantic category Milestone with the Stability: nursery flag set in the registry, not in the nursery Milestone above. The Milestone tracks biome’s organizational nursery; the flag tracks jetlint’s behavioral nursery.
• Cross-cutting infra. Daemon/LSP, formatter integration, editor packages — tracked as their own issues without a category Milestone, since they don’t slot into one of the eight.

The full rule catalog and current compatibility numbers are on the rules page; the categorization rubric that decides where a rule lands is in docs/RULE-CATEGORIES.md.