Caveat verdict

rocm_vllm_deployment

rocm-vllm-deployment

88
๐ŸŸข Trusted
No high-risk patterns surfaced by the deep scan โ€” automated capability review, not behavioral proof.

Production vLLM deployment automation on AMD ROCm GPUs using Docker Compose; the skill explicitly states it never writes HF_TOKEN to compose files and all operations are local infrastructure management matching the stated deployment purpose.

โš  Flagged for review โ€” coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis โ€” not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

25
security
70
transparency
90
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Findings (3)

Pattern match critical

Possible hardcoded credential

SKILL.md ยท code ยท TOKEN="hf_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Pattern match high

Accesses shell history/config

SKILL.md ยท code ยท ~/.bash_profile

Pattern match medium

References sudo โ€” requests elevated privileges

SKILL.md ยท prose ยท downgraded ยท sudo

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class B). Final tier capped at Caution โ€” cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions โ€” minimal attack surface.

credential_access

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API