xcloud-docker-deploy@1.4.1
CAUTION· static onlyPublisher claims: "xCloud Docker Deploy v1.4.1 — a confirmation-gated skill for preparing projects for xCloud. It inspects or changes files only after user consent, generates D..." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-12 and scored it 58/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
…er, generate the proper Dockerfile, Docker image workflow, docker-compose.yml, `.env.example`, and give me the exact xCloud deployment steps. If you already have a…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…er, generates Dockerfile, docker-compose.yml, GHCR GitHub Actions workflow, and .env.example, enforces xCloud-safe port mappings like 80:80 to 3080:80, and can pair…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.4. Generate `.env.example` from all `${VAR}` referencesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- `.env.example`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- `.env.example`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- `.env.example`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.| `xcloud:servers` | Servers, PHP, databases, cron, firewall/fail2ban, sudo users, WordPress provisioning |Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.| `package.json` + `next.config.*` | Next.js | Docker path → use `dockerfiles/nextjs.Dockerfile` + `compose-templates/nextjs-postgres.yml` |Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.- `xcloud:servers` for server capacity, PHP, databases, cron, firewall, sudo users, WordPress provisioningFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
22 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim asif2bd: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Privileged sudo command≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.