Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
project-containerize
v1.0.0对项目进行完整的容器化适配。自动检测分析项目代码和文档,配置和优化代码容器化打包方案,生成专用Dockerfile,生成专用compose.yaml用于快捷部署,输出说明文档,最终生成适配项目的容器化部署方案。触发词:容器化、Docker、docker run、docker-compose、Dockerfile、...
⭐ 0· 31·0 current·0 all-time
byzhu@zhuyifeiruichuang
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's name and description describe project containerization and the included scripts implement that functionality. However, the runtime instructions and scripts assume Docker and Docker Compose are available and run docker/docker-compose commands, yet the skill's metadata does not declare any required binaries. Not declaring Docker/docker-compose is an incoherence between claimed purpose and requested/assumed capabilities.
Instruction Scope
SKILL.md and the bundled scripts instruct the agent to read project files (README, config files, Dockerfiles), copy configuration files into deploy/config/, and run docker/docker-compose commands. Reading and copying config/.env files is expected for containerization, but it means the skill will collect local secrets (e.g., DB passwords, API keys) and place them under deploy/, which broadens its data access beyond just generating Dockerfiles.
Install Mechanism
There is no install spec (instruction-only install), which lowers risk from arbitrary downloads. However, the skill bundle includes multiple Python scripts that will be available to run; there is no declared install step for dependencies (e.g., running those scripts), so the agent or user may execute them directly. That is reasonable for this utility but worth noticing.
Credentials
The skill requests no environment variables or external credentials, which fits its local-file purpose. However, the scripts systematically locate and copy config files (including .env and other files that may contain secrets) into deploy/config and generate a .env template. Copying sensitive files to a new path can unintentionally surface secrets (e.g., if deploy/ is uploaded or committed). No additional credentials are required, so credential overreach is not present, but secret-handling is a proportionality concern.
Persistence & Privilege
The skill is not always-enabled and does not request persistent platform privileges. It writes output into the project's deploy/ directory (its own scope) and does not modify other skills or system-wide agent settings.
What to consider before installing
This skill appears to implement a reasonable containerization workflow, but review these points before installing or running it:
- Docker requirement: The scripts and SKILL.md run docker and docker compose commands but the skill metadata does not declare Docker/Docker Compose as required binaries. Ensure Docker and Docker Compose are installed and be aware the skill will try to execute them.
- Sensitive files handling: prepare_configs.py and related scripts search for and copy configuration files (including .env, application*.yml, logback.xml, etc.) into deploy/config/. That will duplicate any secrets stored in those files into the deploy/ directory. Review and/or remove sensitive files before running, and do not commit deploy/ to version control.
- Review generated artifacts: The skill will generate Dockerfiles, compose files, and deployment scripts that may default to running containers as root and enabling restart policies. Inspect and adjust the generated files (USER, ports, mounts, healthchecks, restart policy) to match your security posture before building or deploying images.
- Execute locally and audit outputs: Run the scripts in a controlled environment (local workstation or isolated CI workspace), and inspect deploy/ and artifacts/ outputs. Avoid running docker-compose up or docker build until you have verified the generated files.
What would change this assessment: if the publisher metadata were updated to declare required binaries (docker/docker-compose) and the scripts were changed to avoid copying raw .env secrets (e.g., only copy sanitized templates or reference originals without duplication), the incoherences noted above would be resolved and confidence could increase.Like a lobster shell, security has layers — review code before you run it.
1.0.0vk978935vhc5dky20gyjtaxvv4n84zr5glatestvk978935vhc5dky20gyjtaxvv4n84zr5g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
