Skip to content
Back to skills

Dependency Advisory Triage

ASecurity

Normalize dependency advisories across native audits and OSV evidence.

  • 8 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 2, 2026
ai-agents

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned September 2, 2026

npx -y skills add Eliyce/paqad-ai --skill dependency-advisory-triage --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dependency Advisory Triage?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dependency Advisory Triage
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/eliyce-dependency-advisory-triage/badge)](https://www.skillsdirectory.com/skills/eliyce-dependency-advisory-triage)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: dependency-advisory-triage
description: Normalize dependency advisories across native audits and OSV evidence.
model_tier: reasoning
triggers:
  - workflow:
      - pentest
cacheable: false
cache_key_inputs:
  - package.json
  - pnpm-lock.yaml
  - package-lock.json
  - composer.lock
output_format: markdown
input_schema:
  advisory_artifact_paths:
    type: path[]
    required: true
    description: Raw audit and advisory artifacts to normalize.
  stack_snapshot_path:
    type: path
    required: false
    description: Optional stack snapshot with installed package versions.
---

## What It Does

Normalizes native package-manager audit output and online advisory results into one dependency finding model so package risk is deduplicated before reporting.

## Use This When

Use this during the pentest workflow after dependency audit scripts and advisory lookups have produced raw artifacts that need to be merged into stable findings.

## Inputs

- Read the raw dependency audit artifacts first.
- Read `references/advisory-normalization.md` before deciding whether two advisories are the same issue.
- Read installed package versions from the stack snapshot when it exists.

## Procedure

1. Run `scripts/normalize-advisories.sh <artifact1> <artifact2> ...` to merge npm/pnpm/OSV outputs into one JSONL stream keyed by (ecosystem, package, advisory_id).
2. For each merged record, write one finding using `assets/output.template.md`.
3. Keep remediation focused on upgrade, replacement, or compensating control.
4. Validate with `scripts/lint-output.sh` — duplicate keys fail the build.

## Output Contract

- Match `assets/output.template.md`: `## Dependency Findings` with `### {{ecosystem}}:{{package}} — {{advisory-id}}` per finding plus Severity/Installed/Sources/Title/Remediation lines.
- Output must pass `scripts/lint-output.sh` (exit 0).

## Escalate / Stop Conditions

- Ask when a package name or installed version cannot be matched to the advisory evidence.
- Warn when audit output and advisory services disagree on whether the package is affected.
- Do not assume a package is fixed just because one advisory source is silent.

## Resources

- `references/advisory-normalization.md`
- `scripts/normalize-advisories.sh`
- `scripts/lint-output.sh`
- `assets/output.template.md`
- `agents/openai.yaml`

Files in this skill

  • SKILL.md2.3 KB
  • agents/openai.yaml146 B
  • assets/output.template.md387 B
  • references/advisory-normalization.md1.6 KB
  • scripts/lint-output.sh1.3 KB
  • scripts/normalize-advisories.sh2.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.