Skip to content
Skills Library
Security · Review & audit

dependency-security

/dependency-security

Managing Supply Chain Security, SBOM generation, and vulnerability patching (SCA). Use when: dependency security.

Repository
gabbe ↗
Licence
CC-BY-4.0
Last repository change
24.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.

Licence

CC-BY-4.0, otwarta.

What it does and when to use it

Managing Supply Chain Security, SBOM generation, and vulnerability patching (SCA). Use when: dependency security.

Original author description

Managing Supply Chain Security, SBOM generation, and vulnerability patching (SCA). Use when: dependency security.

How it works

  1. Goal
  2. Steps
  3. 1. Software Composition Analysis (SCA)
  4. 2. SBOM (Software Bill of Materials)
  5. 3. Dependency Pinning
  6. 4. Typosquatting Defense
  7. Security & Guardrails
Original SKILL.md headings · 40 lines, 467 words
SKILL.md preview
---
name: dependency-security
description: "Managing Supply Chain Security, SBOM generation, and vulnerability patching (SCA). Use when: dependency security."
license: CC-BY-SA-4.0
metadata:
  source: "agents/skills/security/dependency-security.skill.md"
  tags: "security"
  core: "false"
  context_cost: "low"
---
# dependency-security Skill

## Goal
This skill secures the software supply chain.

## Steps
## 1. Software Composition Analysis (SCA)
> "You are what you import."

- **Audit**: Run `npm audit` / `pip-audit` / `cargo audit` in CI.
- **Block**: Fail the build on `CRITICAL` or `HIGH` vulnerabilities.
- **Lock**: Always verify lockfiles (`package-lock.json`) match `package.json`.

## 2. SBOM (Software Bill of Materials)
- Generate a list of all ingredients in your software.
- Tools: `syft`, `cyclonedx-cli`.
- Why? Rapid response when the next Log4Shell happens.

## 3. Dependency Pinning
- **Pin Exact Versions**: Avoid `^1.2.3` in critical apps. Use `1.2.3` to prevent "works on my machine" drift.
- **Private Registry**: For enterprise, proxy public registries to prevent "Left-Pad" incidents.

## 4. Typosquatting Defense
- **Scope**: Use `@myorg/package` scopes.
- **Verify**: Check download counts and maintainer reputation before adding new deps.

## Security & Guardrails

### 1. Skill Security (Dependency Security)
- **Scanner Sandbox Isolation**: Software Composition Analysis (SCA) tools (`npm audit`, `syft`) actively download and parse untrusted third-party manifest files. The agent must execute these scans within an ephemeral, strictly sandboxed container lacking network access to internal company resources, preventing a malicious `package.json` (e.g., via a post-install hook) from compromising the CI/CD pipeline.
- **Lockfile Immutability Enforcement**: The agent is strictly prohibited from bypassing the `package-lock.json` or `yarn.lock` during a build process. It must actively halt any deployment if it detects a divergence between the hashed lockfile and the stated dependencies, effectively blocking dynamic, unvetted code injection at runtime.

### 2. System Integration Security
- **Vulnerability Remediation Prioritization**: The agent must integrate with the overarching threat model. If the SCA tool flags a `CRITICAL` vulnerability in a library (e.g., an image parsing library), but that library is only deployed in a segmented, internal-only, unauthenticated reporting tool, the fix priority is high, but not an immediate block. However, if the vulnerable library touches the public internet, the build MUST fail.
- **Private Registry Mirroring**: To mitigate "Left-Pad" incidents and upstream registry compromises, the architecture must route all dependency pulls through a controlled, internal proxy registry (e.g., Artifactory, Nexus). The agent must flag any configuration that attempts to fetch dependencies directly from the public internet bypassing this proxy.

### 3. LLM & Agent Guardrails
- **Blind Upgrade Traps**: The agent must refuse user prompts that instruct it to blindly "Upgrade all dependencies to `latest` to fix the security warnings." Automated mass upgrades frequently introduce breaking changes or unintentionally pull in typosquatted/poisoned packages. Upgrades must be atomic, tested, and individually verified.
- **Ignoring Critical CVEs**: If a developer prompts the agent to "Add this specific CVE ID to the ignore list so the build passes," the agent must mandate an explicit, documented, and approved risk acceptance justification. It cannot unilaterally suppress critical security warnings based on a casual command.

Versions

RepositoryScoreLicence
This page · andreibesleaga/gabbe90CC-BY-4.0
nahid-sparktales/agent-dispatcher90MIT

Database snapshot: 13.11.2026 · package version 787d2e0cac40 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100supply-chain-security
    Use for software supply-chain security assessment covering SBOM, SCA, CI/CD pipelines, container images, build integrity, dependency provenance, and vulnerability reachability.
  • 100supply-chain-security
    Use for software supply-chain security assessment covering SBOM, SCA, CI/CD pipelines, container images, build integrity, dependency provenance, and vulnerability reachability.
  • 90security-dependencies-and-build
    Assess and remediate dependencies, supply chain, build provenance and secure coding workflow in frontend and associated web services. Use for dependency vulnerability, SCA, lockfile, CI, provenance, build, SBOM.
  • 100security-scanning-security-dependencies
    Scan project dependencies across ecosystems for vulnerabilities, generate SBOMs, assess supply chain risk, and recommend remediation. Use when auditing dependency security or producing an SBOM.
  • 90security-sbom
    Use this skill when asked about SBOM, software bill of materials, dependency graph, SPDX, CycloneDX, supply chain security, component inventory, or dependency analysis. This skill enforces: SBOM generation in CycloneDX/SPDX formats, dependency vulnerability correlation with…
  • 100supply-chain
    Software supply chain security. Covers dependency management, SBOM generation, package integrity verification, and CI/CD security. OWASP A03:2025. USE WHEN: user mentions "supply chain", "dependencies", "npm audit", "SBOM", "vulnerable packages", asks about "dependency…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.