Vibealive

skullzarmy/vibealiveMIT0🔧 1 tools

F4.2SpiderScore (registry)

Full-featured utility to test Next.js projects for unused files and APIs + MCP server

⚠ Hard constraint applied: multiple critical issues forces F
Decision
Not Recommended
Confidence
90%

Vibealive is not recommended — low score (4.18/10) with 14 critical issues.

Recommended Actions

  • high
    Run In Container
    14 critical vulnerabilities require isolation
  • high
    Limit Permissions
    Restrict tool access to minimum required scope

Do Not

  • running in production without container isolation
  • exposing this tool to untrusted input
Risk Flags (1)
  • critical
    child_process_injection×14
    Command injection — execSync() with template literal interpolation
How This Was Decided
  • negativew=0.5Overall quality score = 4.18/10 (grade F)
  • negativew=0.814 critical security issue(s) detected
  • negativew=0.3Tool description clarity score = 1.4/10
Source: SpiderRating automated security scanUpdated: 2026-03-13Protocol: v1.1

Description Quality

Composite: 1.4 / 10

3-Layer Breakdown

Description (38%)
1.4
Security (34%)
5.8
Metadata (28%)
6.0

Description Dimensions

Intent Clarity
0.0
Permission Scope
0.0
Side Effects
2.0
Capability Disclosure
4.0
Operational Boundaries
1.4

Security Analysis

5.8
Score
14
Critical
0
High
0
Medium
0
Low

Findings Redacted

Detailed security findings are hidden during the 90-day responsible disclosure window. Maintainers have been notified.

14 CRITICAL

Metadata Health

Provenance (40%)
9.0
Maintenance (35%)
5.0
Popularity (25%)
2.6

Badge

Add this badge to your README:

[![SpiderRating](https://spiderrating.com/badge/skullzarmy__vibealive.svg)](https://spiderrating.com/servers/skullzarmy/vibealive)