use-railway

Fail

Audited by Runlayer on Mar 7, 2026

Risk Level: HIGH
Scan Summary
Max Score
94%
Files
7
Flagged
6
Chunks
9
Flagged Files (6)
use-railway/references/deploy.mdHIGH
94.2%

Risky tool definition detected

use-railway/scripts/railway-api.shHIGH
91.1%

Risky tool definition detected

Install with: brew install jq"}' exit 1 fi CONFIG_FILE="$HOME/.railway/config.json" if [[ !

use-railway/references/operate.mdMEDIUM
87.8%

Risky tool definition detected

## Health snapshot Start broad, then narrow: ```bash railway status --json # linked context railway service status --all --json # all services, deployment states railway deployment list --limit 10 --json # recent deployments ``` Deployment statuses: `SUCCESS`, `BUILDING`, `DEPLOYING`, `FAILED`, `CRASHED`, `REMOVED`. If everything looks healthy, return a summary and stop.

use-railway/references/configure.mdMEDIUM
86.9%

Risky tool definition detected

Tool: use-railway/references/configure.md [2/2] Description: avoids egress and is faster: ```text BACKEND_URL=http://${{api.RAILWAY_PRIVATE_DOMAIN}}:${{api.PORT}} ``` ### Read current domains Domain configuration lives in `config.services.<service-id>.networking` under `serviceDomains` (Railway-provided) and `customDomains`.

use-railway/references/request.mdLOW
75.0%

Risky tool definition detected

use-railway/SKILL.mdLOW
50.3%

Tool passed security scan

Passed Files (1)Click to expand
use-railway/references/setup.mdOK
46.9%

Tool passed security scan

Audit Metadata
Max File Score
94%
Classification
KNOWN_SERVER_ALL_UNKNOWN
Files Scanned
7
Files Flagged
6
Chunks Analyzed
9
Analyzed
Mar 7, 2026, 11:50 AM
Security Audit — runlayer — use-railway