Versioned security assessment

Report ID: SA-D46E6208

7/7/2026, 9:55:45 PM

sbom-syft security assessment v8

Skill Security Certification Report

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

Highest confirmed finding severity

Critical

3 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.

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.

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

6 Files scanned · 2,022 Lines analyzed

5 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 24 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 18 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 79 evidence locations

Capability review items (2)
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 findings

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

Confirmed security concerns (3)

RISK-001 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.
RISK-002 Medium
SKILL.md:195-201SKILL.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.
RISK-003 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.

Remediation

Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.

  1. FIX-001
    Critical
    Remote installer is piped directly to bash in the CI template.
    Pin the tool version, download a release artifact, verify checksum or signature, and run the installer explicitly.
  2. FIX-002
    Medium
    Cosign installation uses a latest URL without verification.
    Use a package manager or pin a release version and verify the downloaded binary before installation.
  3. FIX-003
    Medium
    Registry credentials are shown in plaintext Syft configuration examples.
    Prefer secret managers or CI secrets, and warn users not to commit configuration files containing credentials.
  4. FIX-004
    Medium
    The CI template uses a mutable GitHub Action branch reference.
    Pin third-party GitHub Actions to immutable commit SHAs or reviewed release tags.

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.

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