vibealive

skullzarmy/vibealive

3.3

If you are the rightful owner of vibealive and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

VibeAlive is a code analysis tool tailored for Next.js applications, focusing on identifying unused code and optimizing project performance.

johnny vibealive

A framework-aware code analysis tool for Next.js projects. Identify unused files, dead code, and redundant API endpoints to keep your codebase clean and maintainable.

Quick Start

# Analyze your Next.js project
npx vibealive analyze .

# Use in different languages
npx vibealive analyze . --locale es  # Spanish
npx vibealive analyze . --locale fr  # French
npx vibealive analyze . --locale de  # German
npx vibealive analyze . --locale pt  # Portuguese

# Start MCP server for IDE integration
npx vibealive serve --stdio

Features

  • Smart Analysis: Detects Next.js versions and routing patterns (App Router, Pages Router, hybrid)
  • Dependency Tracking: Builds complete dependency graph to find orphaned files
  • API Analysis: Identifies unused API endpoints
  • Multiple Formats: Generates JSON, Markdown, and other report formats
  • MCP Integration: Built-in Model Context Protocol server for IDE/LLM integration
  • Build Integration: Webpack plugin and CI/CD pipeline support
  • Focused Scans: Specialized analysis for themes, SEO, performance, and accessibility
  • Internationalization: Multi-language support with community translations

Installation

# Run directly with npx (recommended)
npx vibealive analyze <project-path>

# Or install globally
npm install -g vibealive

Documentation

See the directory for complete documentation:

  • - Features and capabilities
  • - Command-line interface
  • - Integration with IDEs and tools
  • - Automated analysis in CI/CD pipelines
  • - Multi-language support and translation guide

Contributing

We welcome contributions from the community! Please read our for details on:

  • Development setup and workflow
  • Code style and testing requirements
  • Pull request process and review guidelines
  • Types of contributions we're looking for

Please also review our which outlines our community standards and expectations for respectful collaboration.

License

MIT