mcpField
S
security-scan

security-scan

github.com/redpanda-dataSecurity4.3k53 installsUpdated today
Repository

About security-scan

security-scan is a coding skill for resolving npm dependency vulnerabilities reported by Snyk. It guides developers through classifying issues, choosing direct or transitive dependency fixes, and verifying the changes.

Key features

  1. 01Classifies direct and transitive dependencies
  2. 02Checks package and lockfile versions
  3. 03Looks up fixed versions in npm
  4. 04Runs type checks, lint, build, and tests

Use cases

  1. 01Triage a Snyk vulnerability report
  2. 02Fix a vulnerable direct dependency
  3. 03Resolve a vulnerability in a transitive dependency
  4. 04Verify npm security updates

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/redpanda-data/console --skill security-scan

After installing, type/security-scanin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

rules/
_sections.md
_template.md
vuln-direct-deps.md
vuln-transitive-deps.md

Details

From the project README

Security Scan

Resolve npm dependency vulnerabilities detected by Snyk.io security scans.

Activation Conditions

  • User shares Snyk vulnerability reports
  • Mentions CVEs/CWEs
  • Asks to fix security issues in npm dependencies

Quick Reference

ActionRule
Fix direct depsvuln-direct-deps.md
Fix transitive depsvuln-transitive-deps.md

Workflow

1. Assess
  • Parse vulnerability report: package, version, CVE/CWE, severity, fixed version
  • Categorize as direct (in package.json) or transitive (pulled in by another package)
2. Explore
  • Check package.json for current versions and existing overrides
  • Check lockfile for actual resolved versions
  • Search source code for direct usage of vulnerable package
  • Check npm registry for available fixed versions: npm view <package> versions --json
3. Fix

See rules for specific fix patterns.

4. Verify
bun i --yarn
bun run type:check
bun run lint
bun run build
bun run test

All must pass.

Tips

  • Use exact versions for security fixes (no ^ prefix)
  • Fix Critical/High severity first
  • Replace unmaintained packages rather than patching
  • Document workarounds with comments explaining why

Rules

See rules/ directory for detailed guidance.

Comments

Markdown supported