rocm-vllm-deployment@1.0.0
CAUTION· static onlyPublisher claims: "Production-ready vLLM deployment on AMD ROCm GPUs. Combines environment auto-check, model parameter detection, Docker Compose deployment, health verification..." 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-21 and scored it 51/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: Privileged sudo command; 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
| GPU access fails | Add user to `render` group: `sudo usermod -aG render $USER` |Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.2. **Use .env files with chmod 600** — Restrict access to owner onlyFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.- **.env** → `$HOME/vllm-compose/<model-id>/.env` (optional)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.1. **Never commit tokens to version control** — Add `.env` to `.gitignore`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.├── test-results.json $(check_file "$OUTPUT_DIR/test-results.json")Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.2. **Use .env files with chmod 600** — Restrict access to owner onlyFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.4. **Pass tokens at runtime** — `HF_TOKEN=$HF_TOKEN docker compose up -d`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- Permissions: `chmod 600`Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.├── deployment.log $(check_file "$OUTPUT_DIR/deployment.log")Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.├── .env # HF_TOKEN environment (chmod 600, optional)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.├── .env # HF_TOKEN environment (chmod 600, optional)Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.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
29 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim alexhegit: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Privileged sudo command≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- 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.
- Credential pass-through configuration≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
- 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.