Audit History

Version	Date	Result	Review items	Change vs previous
v9 Latest	Jul 23, 2026, 06:47 AM	4 confirmed	3	No capability change
v8	Jul 7, 2026, 09:55 PM	3 confirmed	2	No capability change
v7	Jul 5, 2026, 03:20 AM	2 confirmed	1	No capability change
v6	Jun 28, 2026, 06:14 AM	2 confirmed	0	No capability change
v5	Jan 16, 2026, 04:08 PM	No confirmed findings	0	No capability change
v4	Jan 16, 2026, 04:08 PM	No confirmed findings	0	External commandsNetwork accessFilesystem accessEnv variablesContains scripts
v3	Jan 10, 2026, 11:00 AM	No confirmed findings	0	No capability change
v2	Jan 10, 2026, 11:00 AM	No confirmed findings	0	No capability change
v1	Jan 10, 2026, 11:00 AM	No confirmed findings	0	Baseline

Jul 23, 2026, 06:47 AM

Most detections are false positives caused by Markdown formatting, defensive examples, or fixed local operations. The template still includes a critical pipe-to-shell installer and instructions that download mutable artifacts without integrity verification. It also exposes a GitHub token to an unpinned action and contains CI controls that can fail open.

6

Files scanned

2,022

Lines analyzed

12

Review items

0

False positives ignored

Confirmed security concerns (4)

Critical

assets/ci-config-template.yml:240

Pipe to shell pattern

curl -s https://raw.githubusercontent.com/aquasecurity/tfsec/master/scripts/install_linux.sh | bash

The workflow pipes an unauthenticated, unpinned remote script directly into bash. Upstream compromise or content replacement would produce immediate code execution in CI.

High

assets/ci-config-template.yml:197 SKILL.md:43 SKILL.md:307 SKILL.md:323

Mutable Third-Party Execution References

CI examples use mutable action branches, major tags, and latest container tags, allowing upstream changes to execute without repository review.

The cited examples directly select master, latest, or mutable version tags for code that executes during builds.

High

assets/ci-config-template.yml:61 assets/ci-config-template.yml:123 assets/ci-config-template.yml:128 assets/ci-config-template.yml:235

Fail-Open CI Security Gates

Several scanner commands suppress failures with || true, while later steps only warn, so vulnerable or incomplete builds can continue.

The template explicitly neutralizes multiple scanner exit codes, and some result processing does not enforce the documented severity threshold.

Medium

SKILL.md:195-202 SKILL.md:241-242

Plaintext Registry Credential Guidance

Guidance places registry usernames and passwords in .syft.yaml, increasing accidental commit and local disclosure risk.

The configuration example includes credential fields, and later text recommends adding credentials to that file.

Capability review items (3)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

assets/ci-config-template.yml:240

Hardcoded URL

curl -s https://raw.githubusercontent.com/aquasecurity/tfsec/master/scripts/install_linux.sh | bash

The URL supplies an installation script from a mutable upstream branch. No version pin or integrity check protects the downloaded executable content.

High

assets/ci-config-template.yml:164

Git platform tokens

GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

The workflow passes GITHUB_TOKEN to a third-party action referenced by a mutable major tag. A compromised action revision could misuse the token's workflow permissions.

Medium

SKILL.md:136

Hardcoded URL

wget https://github.com/sigstore/cosign/releases/latest/download/cosign-linux-amd64

The instruction downloads the latest cosign binary without pinning a release or verifying a checksum or signature. Users are then told to execute that artifact.

Risk Factors

⚙️ External commands (50)

🌐 Network access (24)

📁 Filesystem access (4)

assets/ci-config-template.yml:323 assets/ci-config-template.yml:323 SKILL.md:193 SKILL.md:437

🔑 Env variables (23)

⚡ Contains scripts (2)

references/EXAMPLE.md:138 references/EXAMPLE.md:137

Detected Patterns

Pipe to shell pattern

Audited by: codex

Audit version 8

Jul 7, 2026, 09:55 PM

Most static findings are false positives from Markdown examples, defensive reference material, and public documentation links. Confirmed issues remain in supply chain guidance: an unverified curl-to-bash installer, a mutable binary download, plaintext credential examples, and a mutable CI action reference.

6

Files scanned

2,022

Lines analyzed

10

Review items

0

False positives ignored

Confirmed security concerns (3)

Critical

assets/ci-config-template.yml:240

Pipe to shell pattern

curl -s https://raw.githubusercontent.com/aquasecurity/tfsec/master/scripts/install_linux.sh | bash

The CI template fetches a remote installer with curl and immediately pipes it to bash. This executes unverified network content inside the build environment.

Medium

SKILL.md:195-201 SKILL.md:241-243

Plaintext Registry Credential Guidance

The Syft configuration example shows registry username and password fields, then recommends adding credentials to .syft.yaml. Users may copy real registry credentials into a plaintext file.

The cited lines explicitly show credential fields in configuration and later recommend the config-file approach. The risk depends on user handling, so confidence is high but not absolute.

Medium

assets/ci-config-template.yml:196-199

Mutable CI Action Reference

The CI template uses a GitHub Action from the mutable master branch. A changed upstream branch could alter build behavior without review.

The cited workflow references aquasecurity/trivy-action@master directly. Mutable action references are a known CI supply chain risk.

Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

assets/ci-config-template.yml:240

Hardcoded URL

curl -s https://raw.githubusercontent.com/aquasecurity/tfsec/master/scripts/install_linux.sh | bash

The hardcoded raw GitHub URL is used as the source for a shell-piped installer in the CI template. That creates a supply chain risk if the remote script changes or is compromised.

Medium

SKILL.md:136

Hardcoded URL

wget https://github.com/sigstore/cosign/releases/latest/download/cosign-linux-amd64

The skill instructs users to download the latest Cosign Linux binary from a mutable URL, then make it executable and move it into PATH. No checksum or signature verification is shown.

Risk Factors

⚙️ External commands (80)

🌐 Network access (24)

📁 Filesystem access (4)

assets/ci-config-template.yml:323 assets/ci-config-template.yml:323 SKILL.md:193 SKILL.md:437

🔑 Env variables (23)

⚡ Contains scripts (2)

references/EXAMPLE.md:138 references/EXAMPLE.md:137

Detected Patterns

Pipe to shell pattern

Audited by: codex

Audit version 7

Jul 5, 2026, 03:20 AM

Most static findings are false positives from Markdown examples, reference links, or defensive security templates. The CI template contains a confirmed remote installer piped to bash and unpinned scanner installation guidance that should be hardened before publication.

5

Files scanned

2,012

Lines analyzed

8

Review items

2

False positives ignored

Confirmed security concerns (2)

Critical

assets/ci-config-template.yml:240

Pipe to shell pattern

curl -s https://raw.githubusercontent.com/aquasecurity/tfsec/master/scripts/install_linux.sh | bash

The template uses curl piped directly into bash to execute a remote installer in CI. This is unverified remote-code execution if users copy the workflow.

Medium

assets/ci-config-template.yml:57 assets/ci-config-template.yml:119 assets/ci-config-template.yml:170 assets/ci-config-template.yml:197 assets/ci-config-template.yml:230

Unpinned CI Security Tool Installation

The CI template installs security scanners with unpinned package names and a GitHub action pinned to master. Users who copy it inherit supply chain risk from moving upstream releases.

The cited CI lines install scanners without versions or use an action at master. This is a clear template-level supply chain weakness, although exploitation depends on users copying the template.

Capability review items (1)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

assets/ci-config-template.yml:240

Hardcoded URL

curl -s https://raw.githubusercontent.com/aquasecurity/tfsec/master/scripts/install_linux.sh | bash

The URL is used to download an installer from the master branch and pipe it into bash. The network dependency is unpinned and directly executable.

Static false positives ignored (2)

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.

High

references/EXAMPLE.md:276

C2 keywords

- **T1041**: Exfiltration Over C2 Channel

Force-confirmed blocker/high static finding; AI dismissal overridden.

High

references/WORKFLOW_CHECKLIST.md:193

Malware type keywords

[ ] 10. Remove malicious artifacts (malware, backdoors, webshells)

Force-confirmed blocker/high static finding; AI dismissal overridden.

Risk Factors

⚙️ External commands (80)

🌐 Network access (24)

📁 Filesystem access (4)

assets/ci-config-template.yml:323 assets/ci-config-template.yml:323 SKILL.md:193 SKILL.md:437

🔑 Env variables (23)

⚡ Contains scripts (2)

references/EXAMPLE.md:138 references/EXAMPLE.md:137

Detected Patterns

Pipe to shell pattern

Audited by: codex

Audit version 6

Jun 28, 2026, 06:14 AM

Static analysis reported many command, network, environment, filesystem, and script patterns. Review found no malicious intent or prompt injection; most findings are documentation examples or CI templates. Two template patterns remain risky if copied into production without hardening: remote script execution through curl to bash and plaintext registry credential examples.

5

Files scanned

2,012

Lines analyzed

7

Review items

3

False positives ignored

Confirmed security concerns (2)

Medium

assets/ci-config-template.yml:240

Remote Installer Piped to Shell in CI Template

The CI template downloads a tfsec install script from a remote URL and pipes it directly to bash. This appears to be a legitimate IaC scanning example, but it creates supply chain execution risk if users copy it without version pinning or integrity verification.

The exact pipe-to-shell pattern is present in a CI template. Confidence is high for the unsafe pattern, while malicious intent is not supported by the surrounding context.

Medium

SKILL.md:195-201

Plaintext Registry Credential Example

The Syft configuration example shows registry authentication with username and password fields in a .syft.yaml file. The values are placeholders, not real secrets, but users could copy the pattern into a committed repository and expose registry credentials.

The credential fields are visible in the documented configuration example. Confidence is reduced because the values are placeholders and the file also contains general access control guidance.

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.

Low

SKILL.md:41-50 references/WORKFLOW_CHECKLIST.md:71-82

Static Command Findings Are Mostly Tutorial Commands

Most external command findings are markdown examples for running Syft, Docker, Grype, cosign, jq, or CI scanners. They are not hidden execution logic inside the skill runtime, but users should still review commands before running them.

The flagged commands appear in fenced documentation examples and checklist text. No evidence found that the skill executes them automatically.

Low

assets/rule-template.yaml:153-165 references/EXAMPLE.md:135-138 references/EXAMPLE.md:271-279

Vulnerable Code Snippets Are Intentional Examples

Script, secret, weak cryptography, C2 keyword, and injection findings in rule and reference files are intentional vulnerable examples or framework mappings. They support security education and rule templates rather than operational malicious behavior.

The surrounding text labels these snippets as vulnerable examples, remediation patterns, or ATT&CK mappings. No evidence found that these examples are invoked by the skill.

Low

assets/ci-config-template.yml:161-165

GitHub Token Access Is Scoped to a Secrets Scanner Action

The GitHub token pattern appears in a Gitleaks CI action environment block. It uses GitHub Actions secrets syntax for a scanner integration and is not a hardcoded credential in the repository.

The token is referenced through GitHub Actions secrets syntax within a secrets scanning job. No literal token value or exfiltration destination was found at this location.

Risk Factors

⚙️ External commands (3)

SKILL.md:41-50 assets/ci-config-template.yml:240 references/WORKFLOW_CHECKLIST.md:71-82

🌐 Network access (3)

assets/ci-config-template.yml:240 SKILL.md:487-492 assets/rule-template.yaml:42-45

📁 Filesystem access (3)

assets/ci-config-template.yml:321-323 SKILL.md:176-193 SKILL.md:429-438

🔑 Env variables (3)

assets/ci-config-template.yml:161-165 assets/rule-template.yaml:146-165 references/EXAMPLE.md:422-425

⚡ Contains scripts (2)

references/EXAMPLE.md:135-138 assets/rule-template.yaml:153-165

Detected Patterns

Pipe to Shell Installation PatternPlaintext Credential Configuration Pattern

Audited by: codex

Audit version 5

Jan 16, 2026, 04:08 PM

Documentation-only skill providing SBOM generation guidance using Syft CLI tool. No executable code exists in this skill. Static scanner flagged patterns within markdown documentation and YAML templates containing example commands, CI/CD workflows, and security rule templates. All findings are false positives since this skill only contains documentation and templates for legitimate supply chain security workflows.

6

Files scanned

2,228

Lines analyzed

5

Review items

0

False positives ignored

Risk Factors

⚙️ External commands (110)

🌐 Network access (24)

📁 Filesystem access (4)

assets/ci-config-template.yml:323 assets/ci-config-template.yml:323 SKILL.md:193 SKILL.md:437

🔑 Env variables (27)

⚡ Contains scripts (2)

references/EXAMPLE.md:138 references/EXAMPLE.md:137

Audited by: claude

Audit version 4

Jan 16, 2026, 04:08 PM

Documentation-only skill providing SBOM generation guidance using Syft CLI tool. No executable code exists in this skill. Static scanner flagged patterns within markdown documentation and YAML templates containing example commands, CI/CD workflows, and security rule templates. All findings are false positives since this skill only contains documentation and templates for legitimate supply chain security workflows.

6

Files scanned

2,228

Lines analyzed

5

Review items

0

False positives ignored

Risk Factors

⚙️ External commands (110)

🌐 Network access (24)

📁 Filesystem access (4)

assets/ci-config-template.yml:323 assets/ci-config-template.yml:323 SKILL.md:193 SKILL.md:437

🔑 Env variables (27)

⚡ Contains scripts (2)

references/EXAMPLE.md:138 references/EXAMPLE.md:137

Audited by: claude

Audit version 3

Jan 10, 2026, 11:00 AM

Documentation-only skill providing SBOM generation guidance using Syft. No executable scripts, no network calls, no file system access, and no external commands. Pure informational content teaching users how to use the Syft CLI tool for supply chain security.

6

Files scanned

2,012

Lines analyzed

0

Review items

0

False positives ignored

No confirmed security findings were recorded for this completed audit.

Audited by: claude

Audit version 2

Jan 10, 2026, 11:00 AM

Documentation-only skill providing SBOM generation guidance using Syft. No executable scripts, no network calls, no file system access, and no external commands. Pure informational content teaching users how to use the Syft CLI tool for supply chain security.

6

Files scanned

2,012

Lines analyzed

0

Review items

0

False positives ignored

No confirmed security findings were recorded for this completed audit.

Audited by: claude

Audit version 1

Jan 10, 2026, 11:00 AM

Documentation-only skill providing SBOM generation guidance using Syft. No executable scripts, no network calls, no file system access, and no external commands. Pure informational content teaching users how to use the Syft CLI tool for supply chain security.

6

Files scanned

2,012

Lines analyzed

0

Review items

0

False positives ignored

No confirmed security findings were recorded for this completed audit.

Audited by: claude

Version comparison

Confirmed security concerns (4)

Risk Factors

Detected Patterns

Confirmed security concerns (3)

Risk Factors

Detected Patterns

Confirmed security concerns (2)

Risk Factors

Detected Patterns

Confirmed security concerns (2)

Risk Factors

Detected Patterns

Risk Factors

Risk Factors