Versioned security assessment

Report ID: SA-9E952417

7/23/2026, 6:47:12 AM

sbom-syft security assessment v9

Skill Security Certification Report

Audit History
Scanner version 3.0.0 Audit model: codex Latest published report
Skill name
sbom-syft
Version
v0.1.0
Maintainer
AgentSecOps
Coverage
6 Files scanned · 2,022 Lines analyzed
Policy version
skillstore-security-audit-policy-v1

Highest confirmed finding severity

Critical

4 confirmed security findings require attention.

Installation context

Check the current Skill page

This page summarizes report evidence only. The Skill page provides the canonical install advisory.

Open current Skill page

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

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.

Report position

Latest published report

Latest refers to the report sequence, not to artifact currentness.

Audit attestation

Active attestation

A public attestation is available for this exact report.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

6 Files scanned · 2,022 Lines analyzed

7 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

    Commit and path bound

  2. Artifact

    Content and tree hashes bound

  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 50 evidence locations

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

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

Confirmed security concerns (4)

RISK-001 Critical
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.
RISK-002 High
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.
RISK-003 High
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.
RISK-004 Medium
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.

Remediation

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

  1. FIX-001
    Critical
    Remote script is piped directly into bash.
    Install tfsec from a pinned release, then verify its checksum or signature before execution.
  2. FIX-002
    High
    CI actions, images, and downloaded binaries use mutable references.
    Pin actions and images by immutable digest, and pin release versions with published integrity verification.
  3. FIX-003
    High
    Scanner failures and findings can be ignored by the pipeline.
    Separate scanner errors from findings, enforce the configured threshold, and fail when required reports are missing.
  4. FIX-004
    Medium
    Registry credentials are shown in a project configuration file.
    Use a credential helper or CI secret injection, and exclude local secret configuration from version control.

Expert evidence

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

Artifact subject

Marketplace commit
9e952417e76879bc9d853e1b8b2cd6d6d8d4a1c2
Content hash
52220bdb407b36bfd650b1d3412d60bd2e70c3ae9d46302558c83366e0418452
Tree hash
76df3ebc491127172bc7e3280a36d5ef6c825379e6ddac33f8da30220973b8bf
Skill path
skills/agentsecops/sbom-syft
Audit payload hash
c490883e4c01b9d4c2ad3c649c6d83bb

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

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

Audit attestation: active