Skills sbom-syft

📦

sbom-syft

Name: sbom-syft
Author: AgentSecOps

v0.1.0 Content revision r2 Critical ⚙️ External commands🌐 Network access📁 Filesystem access🔑 Env variables⚡ Contains scripts

Generate SBOMs with Syft

Manual software inventories are incomplete and difficult to maintain. This skill guides repeatable Syft SBOM generation for containers, filesystems, archives, and CI pipelines.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Do not auto-install this skill.

The canonical policy requires operator review before any installation action.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "sbom-syft" from https://skillstore.io/skills/agentsecops-sbom-syft.md and its manifest at https://skillstore.io/api/skills/agentsecops-sbom-syft/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/agentsecops-sbom-syft.md Signed manifest GET /api/skills/agentsecops-sbom-syft/manifest Signed lockfile GET /api/skills/agentsecops-sbom-syft/lockfile

Test it

Using "sbom-syft". Create a CycloneDX inventory for the release image and retain it for audit.

Expected outcome:

Target confirmed as the immutable release image digest.
CycloneDX output stored with the release artifacts.
Validation checks confirm the file is readable and contains package components.

Using "sbom-syft". Compare dependencies between two application releases and highlight license changes.

Expected outcome:

Added and removed packages are grouped by ecosystem.
Version changes are listed separately from package additions.
New or changed licenses are flagged for compliance review.

Using "sbom-syft". Prepare a secure CI plan for generating and signing an SBOM.

Expected outcome:

The plan pins tool sources, verifies downloads, generates the SBOM, enforces scan policy, signs the attestation, and retains verification evidence.

Security Audit

Critical

v9 • 7/23/2026 Open versioned report

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.

Files scanned

2,022

Lines analyzed

Review items

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 View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/agentsecops-sbom-syft/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/agentsecops-sbom-syft/security.svg)](https://skillstore.io/skills/agentsecops-sbom-syft?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/agentsecops-sbom-syft?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/agentsecops-sbom-syft/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/agentsecops-sbom-syft.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

AgentSecOps. (2026). sbom-syft security audit report (audit version 9) [Author version 0.1.0]. Skillstore. https://skillstore.io/skills/agentsecops-sbom-syft/audits/9

BibTeX citation

@techreport{agentsecops-agentsecops-sbom-syft-2026,
  author = {AgentSecOps},
  title = {sbom-syft security audit report (audit version 9)},
  institution = {Skillstore},
  year = {2026},
  number = {9},
  url = {https://skillstore.io/skills/agentsecops-sbom-syft/audits/9},
  note = {Author version 0.1.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "sbom-syft security audit report (audit version 9)"
version: "0.1.0"
type: report
authors:
  - name: "AgentSecOps"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/agentsecops-sbom-syft/audits/9"
identifiers:
  - type: other
    value: "skillstore:agentsecops-sbom-syft:audit:9"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Inventory Release Images

Generate CycloneDX and SPDX inventories for each container release and retain them with build artifacts.

Automate Build Evidence

Add repeatable SBOM generation, validation, and artifact retention to an existing delivery pipeline.

Review Dependency Licenses

Extract package and license data for compliance review across applications and container images.

Try These Prompts

Create a Container SBOM

Create a CycloneDX SBOM for <container-image>. Confirm the target, choose a safe output path, and explain how to validate the result.

Scan a Project Directory

Generate an SPDX SBOM for <project-path>. Exclude <patterns>, report detected ecosystems, and identify likely coverage gaps.

Add SBOM Generation to CI

Design a CI job for <platform> that generates an SBOM for <artifact>. Pin dependencies, verify tools, retain outputs, and fail on missing reports.

Build a Signed Supply Chain Workflow

Plan an advanced workflow for <image> that generates multiple SBOM formats, scans vulnerabilities, enforces policy, signs attestations, and verifies published evidence.

Best Practices

Scan immutable image digests and record the matching source revision.
Pin every action, image, and binary, then verify downloaded artifacts before execution.
Store SBOMs as protected release evidence and regenerate them after dependency changes.