Trust Assessment
todo-management received a trust score of 77/100, placing it in the Mostly Trusted category. This skill has passed most security checks with only minor considerations noted.
SkillShield's automated analysis identified 3 findings: 0 critical, 1 high, 1 medium, and 1 low severity. Key findings include Unpinned npm dependency version, Suspicious dependency 'package-lock.json', Unrestricted database path via TODO_DB environment variable.
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.
Last analyzed on February 13, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings3
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| HIGH | Suspicious dependency 'package-lock.json' The `package.json`, `package-lock.json`, and `pnpm-lock.yaml` files declare a dependency named `package-lock.json` itself. This is highly unusual and suggests either a misconfiguration or a typosquatting attempt. A malicious package published under this name could be installed, leading to arbitrary code execution during dependency installation. Remove the `package-lock.json` dependency from `package.json` and `pnpm-lock.yaml`. Ensure only legitimate and necessary dependencies are listed. | LLM | package.json:3 | |
| MEDIUM | Unpinned npm dependency version Dependency 'package-lock.json' is not pinned to an exact version ('^1.0.0'). Pin dependencies to exact versions to reduce drift and supply-chain risk. | Dependencies | skills/lucky-2968/todo-management-1-1-2/package.json | |
| LOW | Unrestricted database path via TODO_DB environment variable The `scripts/todo.sh` script allows the database path to be set via the `TODO_DB` environment variable. An AI agent could be prompted to set this variable to a sensitive file path (e.g., `/etc/passwd`, `/dev/null`). While `sqlite3` will attempt to treat any file as a database, this could lead to corruption or denial of service for the targeted file if it's writable, or prevent the skill from functioning correctly. It does not directly lead to arbitrary file read or code execution. Restrict the `TODO_DB` variable to paths within the skill's designated workspace or a temporary directory. Implement validation to ensure the path is not outside the expected scope (e.g., by checking if it's relative or within a specific allowed directory). | LLM | scripts/todo.sh:3 |
Scan History
Embed Code
[](https://skillshield.io/report/35f39227f915fa66)
Powered by SkillShield