Versioned security assessment

Report ID: SA-2E2009D7

6/28/2026, 6:14:47 AM

sbom-syft security assessment v6

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
sbom-syft
Version
v6
Maintainer
AgentSecOps
Source
github.com/AgentSecOps/SecOpsAgentKit/tree/main/skills/secsdlc/sbom-syft
Coverage
5 Files scanned · 2,012 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

2 confirmed security findings require attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

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.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

5 Files scanned · 2,012 Lines analyzed

2 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Observed in 2 evidence locations

Network access

May connect to external services.

Observed in 3 evidence locations

Filesystem access

May read or write local files.

Observed in 3 evidence locations

Env variables

May read values from the process environment.

Observed in 3 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 3 evidence locations

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (2)

RISK-001 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.
RISK-002 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.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Static false positives ignored (3)
Low
SKILL.md:41-50references/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-165references/EXAMPLE.md:135-138references/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.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable