Skip to content

Bug Risk Detector (Static Heuristics) #3

Description

@sidkr222003

Summary

Create a static analysis feature that highlights risky patterns in code, without full linting.

Why

  • Lightweight alternative to heavy linters
  • Helps catch common issues quickly

Example Patterns

  • == instead of ===
  • Missing await
  • Empty catch blocks

Notes

  • Explanation: Detect common risky code patterns without full linting for a fast, lightweight check.
  • References: ESLint-style heuristics, static analysis rules for ==, missing await, and empty catch blocks.

Acceptance Criteria

  • Highlights at least 3 risk patterns
  • Displays warnings in editor or status bar
  • Easy to extend with additional heuristics

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2-mediumImportant but not urgent. Can be scheduled after high-priority tasks are completed.advancedComplex features involving deep logic, architecture decisions, or integration with multiple systems.documentationImprovements or additions to documentationenhancementNew feature or requestgood first issueBeginner-friendly tasks with clear scope and minimal complexity, ideal for new contributors.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions