審計紀錄
managing-workflow - 6 審計
審計版本 6
最新 中風險Jun 28, 2026, 05:15 PM
The static report overstates risk because many high alerts are false positives from Markdown examples, relative imports, and template placeholders. The real risk is moderate: the skill intentionally runs local Node scripts and those scripts can read, write, or move files based on command arguments without strict path validation.
中風險問題 (2)
低風險問題 (2)
風險因素
⚡ 包含腳本 (5)
📁 檔案系統存取 (8)
🔑 環境變數 (1)
偵測到的模式
審計版本 5
安全Jan 16, 2026, 07:21 PM
This is a legitimate workflow management skill for specification-driven development. All code operates locally within the project .spec directory. No network access, no credential handling, and no external command execution beyond controlled Node.js script invocations. Behavior matches stated purpose.
風險因素
⚡ 包含腳本 (5)
📁 檔案系統存取 (3)
🔑 環境變數 (1)
審計版本 4
安全Jan 16, 2026, 07:21 PM
This is a legitimate workflow management skill for specification-driven development. All code operates locally within the project .spec directory. No network access, no credential handling, and no external command execution beyond controlled Node.js script invocations. Behavior matches stated purpose.
風險因素
⚡ 包含腳本 (5)
📁 檔案系統存取 (3)
🔑 環境變數 (1)
審計版本 3
安全Jan 10, 2026, 11:39 AM
This is a legitimate workflow management skill for specification-driven development. All code operates locally within the project .spec directory. No network access, no credential handling, and no external command execution beyond controlled Node.js script invocations. Behavior matches stated purpose.
風險因素
⚡ 包含腳本 (5)
📁 檔案系統存取 (3)
🔑 環境變數 (1)
審計版本 2
安全Jan 10, 2026, 11:39 AM
This is a legitimate workflow management skill for specification-driven development. All code operates locally within the project .spec directory. No network access, no credential handling, and no external command execution beyond controlled Node.js script invocations. Behavior matches stated purpose.
風險因素
⚡ 包含腳本 (5)
📁 檔案系統存取 (3)
🔑 環境變數 (1)
審計版本 1
安全Jan 10, 2026, 11:39 AM
This is a legitimate workflow management skill for specification-driven development. All code operates locally within the project .spec directory. No network access, no credential handling, and no external command execution beyond controlled Node.js script invocations. Behavior matches stated purpose.