Back to skill

Security audit

maothinking

Security checks for vulnerabilities and agentic risk

Overview

This is a local command-line decision-analysis toolkit with no evidence of hidden data access, network activity, persistence, or destructive behavior.

Reasonable to install if you trust the publisher, preferably in a virtual environment. Avoid installing the optional development requirements unless you pin or audit them first, and treat the tool's recommendations as simple ideological heuristics rather than authoritative advice.

Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Unpinned Dependencies

Low
Category
Supply Chain
Content
# 开发依赖(可选)
pytest>=6.0
pytest-cov>=3.0
black>=22.0
flake8>=4.0
mypy>=0.950
Confidence
90% confidence
Finding
black is specified as an unpinned dependency and there are known advisories affecting some versions, so a fresh install may resolve to a vulnerable release. This elevates the usual reproducibility concern into a real supply-chain security issue, especially in CI or developer environments that process untrusted files.

Known Vulnerable Dependency: black — 3 advisory(ies): CVE-2026-32274 (Black: Arbitrary file writes from unsanitized user input in cache file name); CVE-2024-21503 (Black vulnerable to Regular Expression Denial of Service (ReDoS)); CVE-2024-21503 (Versions of the package black before 24.3.0 are vulnerable to Regular Expression)

High
Category
Supply Chain
Confidence
95% confidence
Finding
black is declared without an upper bound or exact pin, and the analysis reports multiple known advisories affecting some versions, including arbitrary file write and ReDoS issues. If this dependency is installed in CI or developer workflows that process attacker-controlled inputs, vulnerable versions could be pulled in and exploited.

Static analysis

No suspicious patterns detected.