Back to skill

Security audit

DevLog Agent Skill

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward local developer-journaling helper, but users should understand that it installs an external CLI and stores project notes persistently.

Install only if you are comfortable with a user-level PyPI dependency and persistent local project logs. Keep secrets, tokens, customer information, and highly sensitive internal notes out of log entries, and consider reviewing or pinning dev-log-cli before running setup.sh in sensitive environments.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T08 · Insecure Dependencies

Warning
Location
setup.sh:10
Finding

Automatic Installation of Unpinned Third-Party Dependencies

Content
View full analysis
/dev/null then echo "Error: Failed to install pipx automatically." echo "Please install it manually: https://github.com/pypa/pipx#install-pipx" exit 1 fi fi echo "Installing dev-log-cli via pipx..." pipx install dev-log-cli ``` ### Technical Analysis The setup script installs both `pipx` and `dev-log-cli` without specifying reviewed versions or verifying artifact integrity. Consequently, the exact code installed depends on mutable package-index state at execution time. Python packages may execute package-controlled build or installation logic. The installed `devlog` executable also runs package-controlled code whenever the skill invokes it. If the package repository, maintainer account, release pipeline, or a transitive dependency is compromised, the setup process could retrieve and execute code that was not present during this audit. The use of the standard package names does not establish that either package is currently malicious. The vulnerability is the absence of version constraints, hashes, provenance verification, and an explicit trust boundary before automatic installation. ### Attack Path 1. An attacker compromises a relevant package maintainer account, package-index release, build pipeline, or transitive dependency. 2. The attacker publishes a malicious or modified release under a dependency name used by the script. 3. A user runs `setup.sh` on a system where `pipx` or `devlog` is absent. 4. The unpinned installation commands retrieve the current package-index versions. 5. Package-controlled code execut ...[truncated 1017 chars]
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Context Leakage

High
Category
Data Exfiltration
Confidence
80% confidence
Finding

The skill explicitly encourages agents to 'capture context' and store project milestones, blockers, and searchable history in a local database. Without clear data-minimization guidance, agents may log sensitive code details, secrets, internal incident notes, or proprietary project context, creating a persistent local source of information leakage.

Content

Scanner excerpt · SKILL.md (reported line 6)May include surrounding context.

md
A standardized journaling skill for OpenClaw agents to track progress, tasks, and project status using `dev-log-cli`.

## Description
This skill enables agents to maintain a professional developer log. It's designed to capture context, project milestones, and task statuses in a structured SQLite database.

## Requirements
- `dev-log-cli` (installed via `pipx`)

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
92% confidence
Finding

The markdown states that the skill stores progress, milestones, and task statuses in a structured SQLite database, and later shows add/edit commands, but it does not explicitly warn users that invoking the skill will create or modify persistent local records. Because this behavior affects user/project data retention, the skill description should disclose it clearly.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.