Skip to content
VibeLint logo

VibeLint

Scans code writes and agent tool calls before execution, blocking unsafe patterns and requiring approval for sensitive actions.

Developer toolsSecuritySecurityAgentsCode generation
vibelint.dev ↗Launched on Product Hunt · 2026-04-07
At a glanceswept 2026-09-19
Price
Price not read
Use
Emerging
Activity
Actively maintainednothing dated on the site
Company
founding year not on record
Alternatives in Developer toolsby use, among tools still maintained
  • GreptileReviews pull requests and tests code changes using agent swarms to catch bugs and style violations across codebases.

    Established

    ≈ 8.5k visits/mo
  • Noah LabsAI IDE for regulated industries with airgapped operation, formal verification, and policy-aware code generation.

    Emerging

    ≈ 110 visits/mo
  • Fluid AttacksScans applications for vulnerabilities using automated analysis and human penetration testing, prioritizes findings by exploitability, and generates remediation guidance.

    not read yet

    ≈ 4.3k visits/mo
  • KiroConverts prompts into executable specifications and implements code with parallel agents that validate correctness.

    Widely usedActively maintained

    ≈ 32.7k visits/mo
  • DevinExecutes software engineering tasks including code migrations, bug fixes, testing, and documentation generation across multiple repositories.

    Widely usedActively maintained

    ≈ 30.6k visits/mo
  • ReplitBuilds and deploys web apps, websites, and agents from natural language descriptions.

    Widely used

    ≈ 278k visits/mo

All Developer tools tools →

Questions this page answers
  • What is VibeLint?

    Scans code writes and agent tool calls before execution, blocking unsafe patterns and requiring approval for sensitive actions.

  • Do people use VibeLint?

    Emerging.

  • Is VibeLint still maintained?

    Actively maintained.

  • What are alternatives to VibeLint?

    In Developer tools, by use: Greptile, Noah Labs, Fluid Attacks, Kiro, Devin, Replit.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.