Audit History

Most alerts are false positives from Markdown, reference links, placeholder credentials, and examples labeled as insecure. Actionable risks include unsafe CI filename handling and unverified latest-binary downloads. Mutable CI dependencies add supply-chain exposure, while no prompt injection or malicious intent was found.

Most static findings are false positives caused by Markdown code fences, reference URLs, taxonomy labels, and labeled Dockerfile examples. The real issue found is supply-chain exposure from downloading a latest Hadolint executable without checksum verification in the install guidance and CI template. No prompt injection, credential exfiltration intent, or malicious automation was found.

Most static alerts are false positives caused by Markdown examples, Hadolint rule text, placeholder secrets, and Dockerfile cache cleanup snippets. The only confirmed issues are hardening concerns in copyable workflow or install examples: an unsafe GitHub Actions path list pattern and unpinned latest binary downloads. No prompt injection, covert exfiltration intent, or malicious skill behavior was found.

Most static alerts are false positives caused by Markdown examples, Hadolint rule text, placeholder secrets, and Dockerfile cache cleanup snippets. The only confirmed issues are hardening concerns in copyable workflow or install examples: an unsafe GitHub Actions path list pattern and unpinned latest binary downloads. No prompt injection, covert exfiltration intent, or malicious skill behavior was found.

The static analyzer reported many severe patterns, but review shows most are Markdown examples or Hadolint configuration references, not hidden malicious behavior. The skill is safe to publish with a warning because it encourages external command execution and includes an unverified network installer pattern.

This is a pure documentation skill with no executable code. All 200 static findings are false positives triggered by documentation examples showing Dockerfile patterns. The skill provides legitimate security documentation for Hadolint, an open-source Dockerfile linter. No scripts, network calls, or filesystem modifications exist. Behavior matches the stated purpose of Dockerfile security linting guidance.

This is a pure documentation skill with no executable code. All 200 static findings are false positives triggered by documentation examples showing Dockerfile patterns. The skill provides legitimate security documentation for Hadolint, an open-source Dockerfile linter. No scripts, network calls, or filesystem modifications exist. Behavior matches the stated purpose of Dockerfile security linting guidance.

This is a pure documentation and configuration skill with no executable code. The skill provides guidance for using Hadolint, an open-source Dockerfile linter, along with CI/CD templates and configuration files for container security validation. No scripts, network calls, or file system access beyond reading user-provided Dockerfiles. All behavior matches the stated purpose of Dockerfile security linting.

This is a pure documentation and configuration skill with no executable code. The skill provides guidance for using Hadolint, an open-source Dockerfile linter, along with CI/CD templates and configuration files for container security validation. No scripts, network calls, or file system access beyond reading user-provided Dockerfiles. All behavior matches the stated purpose of Dockerfile security linting.

This is a pure documentation and configuration skill with no executable code. The skill provides guidance for using Hadolint, an open-source Dockerfile linter, along with CI/CD templates and configuration files for container security validation. No scripts, network calls, or file system access beyond reading user-provided Dockerfiles. All behavior matches the stated purpose of Dockerfile security linting.