Megamemory

0xK3vin/MegaMemoryMITโญ 69๐Ÿ”ง 9 tools

F2.0SpiderScore (registry)
โš  Hard constraint applied: critical vulnerability
Decision
Not Recommended
Confidence
90%

Megamemory is not recommended โ€” low score (2.0/10) with 1 critical issues.

Recommended Actions

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

Do Not

  • โœ—running in production without container isolation
  • โœ—using for security-sensitive tasks
Risk Flags (3)
  • critical
    child_process_injection
    Command injection รขโ‚ฌโ€ execSync() with non-literal command
  • high
    ts_path_traversalร—2
    Potential path traversal -- user input used in file system operations
  • medium
    ts_input_reflection
    User input reflected directly in tool output -- may enable prompt injection via reflection
How This Was Decided
  • negativew=0.5Overall quality score = 2.0/10 (grade F)
  • negativew=0.81 critical security issue(s) detected
  • negativew=0.52 high-severity issue(s) detected
  • negativew=0.3Tool description clarity score = 3.1/10
Source: SpiderRating automated security scanUpdated: 2026-03-21Protocol: v1.1

Description Quality

Composite: 3.1 / 10

3-Layer Breakdown

Description (38%)
3.1
Security (34%)
6.6
Metadata (28%)
7.0

Description Dimensions

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

Security Analysis

6.6
Score
1
Critical
2
High
1
Medium
0
Low

Findings Redacted

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

1 CRITICAL1 MEDIUM2 HIGH

Metadata Health

Provenance (40%)
7.0
Maintenance (35%)
8.0
Popularity (25%)
5.8

Badge

Add this badge to your README:

[![SpiderRating](https://spiderrating.com/badge/0xK3vin__MegaMemory.svg)](https://spiderrating.com/servers/0xK3vin/MegaMemory)