Alph is rated NOT_RECOMMENDED by SpiderRating. Alph is not recommended — low score (2.0/10) with 5 critical issues.

What are the security risks of Alph?

Key risk flags: child_process_injection (critical), ts_path_traversal (high), token_leakage (high). Overall security score: 6.0/10 with 5 critical issues.

Are there safer alternatives to Alph?

Similar tools include: upbound/marketplace-mcp-server, tenkoh/recent-go-mcp, Martian-Engineering/maniple. View full comparison at spiderrating.com.

Alph

Aqualia/AlphMIT⭐ 62🔧 0 tools

F2.0SpiderScore (registry)

Use cases:git-ops package-registry

⚠ Hard constraint applied: critical vulnerability

Decision

Not Recommended

Confidence

90%

Alph is not recommended — low score (2.0/10) with 5 critical issues.

Recommended Actions

high
Run In Container
5 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
✗using for security-sensitive tasks

Risk Flags (5)

critical
child_process_injection×5
Tainted command injection â€” user input flows to shell execution
high
ts_path_traversal×7
Potential path traversal -- user input used in file system operations
high
token_leakage×2
Secret or token may be leaked through error messages, logs, or return values
medium
ts_input_reflection×5
User input reflected directly in tool output -- may enable prompt injection via reflection
medium
input_reflection
User input reflected directly in tool output -- may enable prompt injection via reflection