Security audit
Security checks for vulnerabilities and agentic risk
This looks like a local deployment logbook rather than a real PHP deployment tool, and it persistently saves whatever users type into local files.
Install only if you want a local plaintext deployment activity log. Do not enter API keys, passwords, tokens, private host details, or other secrets, because entries are saved under ~/.local/share/deploy-tool. Treat it as a logging helper, not as a PHP framework deployment/provisioning tool.
The skill’s declared identity as a PHP deployment/provisioning tool does not match the documented behavior, which is a local Bash logging utility that writes persistent data under the user’s home directory. This kind of capability mismatch is dangerous because users or orchestrators may grant trust or invoke the skill under false assumptions, leading to unintended data persistence and misuse in automation contexts.
The script advertises itself as a PHP deployment utility, but the visible functionality is a generic local data logger with help text designed to resemble a deployment tool. This mismatch is dangerous because users may grant trust, provide sensitive deployment-related inputs, or install the tool in privileged workflows under false pretenses.
The core commands accept arbitrary user input and persist it to local files instead of performing the deployment operations implied by the skill metadata. In a deployment context, users may enter hostnames, tokens, credentials, repository data, or operational notes, causing silent retention of sensitive information unrelated to the promised function.
The top-level documentation is internally contradictory, alternating between 'PHP deployment tool' and a generic deployment-entry logging toolkit. Such contradictions undermine operator understanding and security review, making it easier for unexpected capabilities like local persistence to slip through approval or be used in the wrong context.
The manifest markets the skill as a PHP deployment tool, but the body describes only a Bash-based note-taking/logging utility. This semantic mismatch can mislead users, reviews, or policy engines into authorizing a skill for one purpose while it performs another, which increases the risk of inappropriate deployment in privileged environments.
The skill persistently stores user-provided entries and exports them to predictable locations in the home directory, creating a risk of sensitive operational data being retained longer than expected. In deployment contexts, logged inputs may include environment names, release details, hostnames, or other confidential information, so undocumented session persistence materially increases exposure.
All data is stored locally in `~/.local/share/deploy-tool/`:
- **Per-command logs** — Each command (run, check, convert, etc.) writes to its own `.log` file with pipe-delimited `timestamp|value` format.
- **history.log** — A unified activity log recording every write operation with timestamps.
- **Export formats** — The `export` utility function supports JSON, CSV, and TXT output, written to `~/.local/share/deploy-tool/export.<fmt>`.
No external services, databases, or API keys are required. Everything is flat-file and human-readable.
The inline description markets the script as a deployment tool, while the code behavior is limited to recording and exporting entries. Misleading labeling increases the chance that operators will trust the tool with sensitive deployment data or integrate it into automation pipelines without understanding its real behavior.
The export feature aggregates all stored log contents into additional files without clear disclosure that historical activity data will be copied and potentially broaden exposure. This increases the blast radius of previously collected sensitive data by duplicating it into JSON, CSV, or text outputs that may be shared or left behind.
User-supplied input is written verbatim into persistent log files under the user's home directory with no privacy notice, sensitivity filtering, or retention controls. In the context of a supposed deployment tool, this can capture secrets, infrastructure identifiers, and operational data that users may reasonably expect not to be stored.
No suspicious patterns detected.