Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Supply Chain Security

    1

    Audit dependencies, CI tokens and build provenance by reachability, not CVE spam

    $17

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Supply Chain Security

    Supply Chain Security

    Example session with this skill installed

    Review this repository's software supply chain before release. Inspect the package manifests, lockfile, CI workflow, third party actions, token permissions, and build provenance. Prioritize dependency advisories by actual reachability and do not modify any files.

    • Read your context and instructions
    • Compiled the supply chain security

    Illustrative synthetic demo. It demonstrates the expected review structure. No external registry, production repository, CI account, or live advisory service was contacted.

    Supply Chain Review Record

    SCOPE

    Synthetic Node.js repository with a package manifest, lockfile, and CI workflow.

    Finding SC-01

    Area

    CI token permissions

    Synthetic observation

    The illustrative workflow grants write permission to repository contents for a job that only installs dependencies and runs tests.

    Risk

    The job has broader authority than required. If a dependency installation step or third party action were compromised, the excessive token permission would increase potential impact.

    Recommended control

    Reduce the job token to the minimum permissions required for testing.

    Priority

    HIGH IN SYNTHETIC EXAMPLE

    Finding SC-02

    Area

    Dependency advisory

    Synthetic observation

    A transitive package is modeled as having a published advisory affecting an optional parsing feature.

    The supplied synthetic application path does not import or invoke that feature.

    Reachability

    NOT ESTABLISHED AS REACHABLE

    Disposition

    Do not classify the advisory as an exploitable application finding solely from version presence. Track the upgrade and verify whether the affected function becomes reachable elsewhere.

    Finding SC-03

    Area

    Build provenance

    Synthetic observation

    The example workflow produces a release artifact but does not record a verifiable relationship between the artifact, source revision, and build execution.

    Risk

    Consumers and release operators have limited ability to establish where the artifact came from.

    Recommended control

    Record build provenance tied to the source revision and release artifact.

    SBOM Readiness

    Dependency inventory

    AVAILABLE FROM SYNTHETIC LOCKFILE

    Artifact relationship

    INCOMPLETE

    Result

    PARTIAL

    Review Boundary

    No package was upgraded.

    No CI workflow was modified.

    No registry was contacted.

    No credential or token value was inspected.

    No artifact was published.

    Priority Summary

    1. Reduce unnecessary CI token authority.
    2. Establish build provenance for release artifacts.
    3. Track the modeled dependency advisory without claiming exploitability until reachability is established.

    Next Step

    Route approved corrective changes through the appropriate remediation and implementation workflow, then verify the resulting controls before release.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Reviews the software supply chain behind an application, including dependencies, lockfiles, package registries, CI workflows, build provenance, token permissions, and SBOM readiness. It prioritizes risks by reachability and operational exposure instead of treating every advisory as an equally urgent vulnerability.

    What it does

    • Reviews direct and transitive dependencies together with their lockfiles.
    • Examines package registry usage and dependency resolution controls.
    • Reviews CI and build workflows for excessive token permissions and unsafe trust boundaries.
    • Evaluates artifact provenance and build integrity controls.
    • Assesses SBOM readiness and dependency inventory quality.
    • Triages dependency advisories based on whether affected functionality is actually reachable.
    • Identifies risky build, release, and dependency patterns that increase supply chain exposure.
    • Produces prioritized findings with evidence, impact, and remediation direction.

    How it works

    1. Inventory identifies package manifests, lockfiles, build workflows, registries, and release paths.
    2. Dependency analysis maps direct and transitive packages and identifies relevant advisories.
    3. Reachability analysis determines whether affected functionality is present in a meaningful execution path.
    4. CI review evaluates workflow triggers, third party actions, token permissions, secrets boundaries, and artifact handling.
    5. Provenance review checks how artifacts are built, identified, and promoted.
    6. Reporting separates confirmed exposure from advisory noise and records the smallest relevant remediation path.

    Frameworks and structure

    The workflow uses OWASP SCVS and NIST SSDF concepts to organize supply chain review areas while keeping findings tied to the actual repository and build context.

    Boundaries

    This skill focuses on software supply chain and build pipeline security.

    Application code vulnerabilities belong to secure-code-review. Runtime security configuration belongs to security-config-review. Secrets and cryptographic handling inside the application belong to data-secrets-crypto-review.

    It does not automatically upgrade dependencies, rewrite CI workflows, rotate tokens, publish artifacts, or modify registries.

    Why this beats prompting it yourself

    Generic dependency reviews often produce long CVE lists without showing whether the vulnerable functionality is reachable or whether the advisory materially affects the project. They may also ignore CI permissions, provenance, and build trust entirely. This skill treats the supply chain as a complete path from dependency resolution to artifact production and prioritizes what can actually affect the software.

    Validation

    This skill is part of the JetFerrari Security Engineering stack and is covered by the stack's structural, routing, installation, discovery, and behavioral validation. No unsupported individual runtime qualification is claimed here.

    Use cases

    • Review dependency and lockfile risk before a release.
    • Triage dependency advisories by actual reachability.
    • Audit GitHub Actions or similar CI workflows for excessive permissions.
    • Review third party actions and build trust boundaries.
    • Assess artifact provenance and SBOM readiness.
    • Identify supply chain controls that should be strengthened before release.

    Known limitations

    The quality of the review depends on the manifests, lockfiles, CI workflows, registry configuration, build metadata, and advisory information available to the agent. Reachability may remain unverified when runtime paths or dependency usage cannot be established. The skill does not automatically update packages, rotate credentials, modify CI configuration, or publish artifacts.

    Part of JetFerrari Security Engineering.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    The quality of the review depends on the manifests, lockfiles, CI workflows, registry configuration, build metadata, and advisory information available to the agent. Reachability may remain UNVERIFIED when runtime paths or dependency usage cannot be established. External advisory data may also be unavailable or incomplete. The skill does not automatically upgrade packages, rotate credentials, modify CI configuration, publish artifacts, or write to package registries.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Permissions

    Terminal / Shell
    Read Files
    Browser
    Network Access

    Access is limited to dependency manifests, lockfiles, CI and build configuration, repository context, and relevant public advisory or registry information. The skill does not modify project files, upgrade dependencies, rotate credentials, change CI settings, inspect secret values, publish artifacts, or write to package registries.

    Listed24 days ago

    What's inside

    Frequently Asked Questions

    It reviews the security of the software supply chain from dependency resolution through CI and artifact production, prioritizing meaningful exposure instead of treating every dependency advisory as equally urgent.

    Use it before a release, when dependency advisories appear, when reviewing CI security, when introducing third party actions or packages, or when evaluating build provenance and SBOM readiness.

    A scanner primarily identifies packages associated with advisories. Supply Chain Security also examines reachability, lockfiles, registry behavior, CI permissions, third party actions, provenance, and build trust boundaries so findings can be prioritized by actual project exposure.

    No. The review is read only. It identifies and prioritizes risks but does not upgrade packages, change workflows, rotate tokens, or publish artifacts.

    Provide the relevant repository context, especially package manifests, lockfiles, CI or build configuration, and release information. Public advisory or registry access can improve verification but is not required for the workflow to identify evidence gaps.

    New in DevOps & Cloud