Back to skill

Security audit

Taskify CLI

Security checks for vulnerabilities and agentic risk

Overview

This skill is a coherent Taskify CLI guide, but users should review the third-party npm package and be careful with destructive board commands.

Before installing, verify the taskify-nostr npm package and source repository, prefer the user-local install form when possible, and avoid running destructive board cleanup or column deletion commands unless you have confirmed the target board and understand recovery options. Do not use Taskify agent commands on sensitive boards unless the configured AI backend is trusted or self-hosted.

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
SKILL.md:14
Finding

Unpinned Global Installation of a Third-Party Executable

Content
View full analysis
Remediation
View remediation
``` 2. Record the reviewed package version, source commit, and expected npm integrity digest in the Skill documentation. 3. Verify that the npm artifact corresponds to the reviewed source release before installation. 4. Prefer an isolated, project-local, containerized, or dedicated user-local installation over a global installation. 5. Avoid recommending `sudo npm install -g`; the package should not receive administrator privileges. 6. Where compatible with the package, install with lifecycle scripts disabled: ```bash npm install --ignore-scripts --prefix ~/.local -g taskify-nostr@ ``` If lifecycle scripts are required, review each script before allowing it to run. 7. Re-audit the pinned release and its transitive dependencies whenever the documented version is updated. 8. Require explicit user approval before installation rather than allowing an agent to install or upgrade the package automatically. ]]>
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • 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)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

This markdown file documents taskify board clear-completed <board> as deleting all completed tasks, but provides no warning about data loss, reversibility, or need for confirmation. Under the markdown variant of SQP-2, destructive behavior affecting user data should be accompanied by an explicit warning.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
78% confidence
Finding

The reference lists commands such as board leave, board archive, board hide, and column-delete without explaining their effects on local configuration, visibility, or recoverability. Because this is user-facing markdown for commands that may remove access or delete structure, the description should warn users about those impacts.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.