moai-baas-railway-ext
Audited by Socket on Mar 2, 2026
1 alert found:
SecurityThis skill is coherent with its stated purpose (deployment, orchestration, and environment management on Railway) and uses expected mechanisms: CI workflow with RAILWAY_TOKEN, Context7 for documentation, Railway clients for environment/config updates, and standard package/Docker usage. There are no direct signs of malicious code (no obfuscated payloads, no curl|bash download-execute or suspicious external endpoints). However, the skill performs high-privilege actions (writing secrets, deploying, scaling) that are appropriate for its role but pose supply-chain and credential risks if misused or if dependencies/CLIs are compromised. Key areas to harden: restrict and rotate CI tokens, ensure railway_client.set_environment_variables uses secure storage and least privilege, avoid logging raw SQL, and pin or audit third-party CLI/dependency versions. Overall, I assess low likelihood of intentional malware (malware: 0.05) but moderate supply-chain and credential risk (securityRisk: 0.55).