Audit History

All 81 Ruby or shell backtick alerts are false positives caused by Markdown and BigQuery identifier syntax, and both reconnaissance alerts are benign guidance. Two fixed /tmp writes remain confirmed, while semantic review found overbroad metadata authorization and disclosure of organization-specific cloud identifiers.

The static Ruby backtick and temp-file findings are false positives caused by Markdown examples, SQL backticks, and documented bq commands. Semantic review found high-risk organization-specific BigQuery guidance that names Monzo projects and includes workflows for sampling or exporting data. No prompt injection text or covert malware behavior was found.

Most static command findings are false positives caused by Markdown or SQL backticks, not Ruby shell execution. Two temp-file writes are real medium-risk examples, and semantic review found high-risk organization-specific BigQuery access guidance involving named sensitive projects.

Manual review found that the static Ruby backtick, weak-crypto, and reconnaissance alerts are mostly false positives caused by Markdown code examples and prose. The confirmed risk is contextual: the skill gives target-specific BigQuery project, dataset, PII, and export guidance that should not be published broadly without sanitization and authorization controls.

Pure documentation skill containing only Markdown guidance for BigQuery CLI usage. All detected patterns are false positives: bash command examples in documentation, repository URLs in metadata, and file paths in safe query patterns. The skill explicitly promotes safe data practices including INFORMATION_SCHEMA queries and data sensitivity guidelines.

Pure documentation skill containing only Markdown guidance for BigQuery CLI usage. All detected patterns are false positives: bash command examples in documentation, repository URLs in metadata, and file paths in safe query patterns. The skill explicitly promotes safe data practices including INFORMATION_SCHEMA queries and data sensitivity guidelines.

Pure documentation skill containing only Markdown guidance. No executable code, scripts, network calls, or file system access. Promotes safe data practices with explicit warnings about sensitive data handling.

Pure documentation skill containing only Markdown guidance. No executable code, scripts, network calls, or file system access. Promotes safe data practices with explicit warnings about sensitive data handling.

Pure documentation skill containing only Markdown guidance. No executable code, scripts, network calls, or file system access. Promotes safe data practices with explicit warnings about sensitive data handling.