Audit History
scribe-mcp-usage - 9 audits
Version comparison
Capability and finding changes across audited versions, newest first.
| Version | Date | Result | Review items | Change vs previous |
|---|---|---|---|---|
| v9 Latest | Jul 6, 2026, 07:31 AM | 2 confirmed | 0 | No capability change |
| v8 | Jul 6, 2026, 07:31 AM | 2 confirmed | 0 | No capability change |
| v7 | Jun 29, 2026, 03:06 AM | 2 confirmed | 0 | External commandsFilesystem accessEnv variables |
| v6 | Jan 21, 2026, 04:23 PM | 1 confirmed | 0 | Filesystem accessExternal commandsEnv variables |
| v5 | Jan 16, 2026, 11:21 PM | No confirmed findings | 0 | No capability change |
| v4 | Jan 16, 2026, 11:21 PM | No confirmed findings | 0 | Filesystem accessExternal commandsEnv variables |
| v3 | Jan 10, 2026, 12:32 PM | No confirmed findings | 0 | No capability change |
| v2 | Jan 10, 2026, 12:32 PM | No confirmed findings | 0 | No capability change |
| v1 | Jan 10, 2026, 12:32 PM | No confirmed findings | 0 | Baseline |
Jul 6, 2026, 07:31 AM
The static analyzer findings are false positives caused by Markdown code spans, fenced examples, placeholder paths, and an environment variable name used in documentation. Manual review found semantic risk from coercive prompt-language and mandatory reasoning/activity logging that can override user intent and collect sensitive details.
Confirmed security concerns (2)
Risk Factors
⚙️ External commands (149)
📁 Filesystem access (18)
🔑 Env variables (1)
Jul 6, 2026, 07:31 AM
The static analyzer findings are false positives caused by Markdown code spans, fenced examples, placeholder paths, and an environment variable name used in documentation. Manual review found semantic risk from coercive prompt-language and mandatory reasoning/activity logging that can override user intent and collect sensitive details.
Confirmed security concerns (2)
Risk Factors
⚙️ External commands (149)
📁 Filesystem access (18)
🔑 Env variables (1)
Jun 29, 2026, 03:06 AM
Static command, filesystem, and environment hits are mostly false positives caused by Markdown examples, placeholder paths, and variable names. The substantive risk is prompt-style authority language that tells agents to treat the skill as non-negotiable policy and to log broad work details. No evidence found of bundled executable code, network exfiltration, or confirmed malicious intent.
Confirmed security concerns (2)
Static false positives ignored (3)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
Risk Factors
⚙️ External commands (3)
📁 Filesystem access (3)
🔑 Env variables (1)
Detected Patterns
Jan 21, 2026, 04:23 PM
All static findings are false positives. The skill is documentation for the Scribe MCP tool which manages project documentation. Detected patterns are documentation references, markdown formatting, and metadata - not actual security vulnerabilities.
Confirmed security concerns (1)
Jan 16, 2026, 11:21 PM
AI analysis failed after multiple attempts - MANUAL REVIEW REQUIRED before publishing. This skill cannot be auto-published until reviewed by a human.
Risk Factors
📁 Filesystem access (21)
⚙️ External commands (249)
🔑 Env variables (1)
Detected Patterns
Jan 16, 2026, 11:21 PM
AI analysis failed after multiple attempts - MANUAL REVIEW REQUIRED before publishing. This skill cannot be auto-published until reviewed by a human.
Risk Factors
📁 Filesystem access (21)
⚙️ External commands (249)
🔑 Env variables (1)
Detected Patterns
Jan 10, 2026, 12:32 PM
Pure documentation file (SKILL.md) providing guidance for AI agents. No executable code, no network calls, no file access, no credentials. Describes MCP tool usage but does not perform operations itself.
Jan 10, 2026, 12:32 PM
Pure documentation file (SKILL.md) providing guidance for AI agents. No executable code, no network calls, no file access, no credentials. Describes MCP tool usage but does not perform operations itself.
Jan 10, 2026, 12:32 PM
Pure documentation file (SKILL.md) providing guidance for AI agents. No executable code, no network calls, no file access, no credentials. Describes MCP tool usage but does not perform operations itself.