pnpm-audit-alert-issue

Normalize pnpm audit JSON output into structured findings with dependency paths.

Updated May 31, 2026
One-click install
npx skills add https://github.com/shoji9x9/skills --skill pnpm-audit-alert-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pnpm-audit-alert-issue
Source: https://github.com/shoji9x9/skills/tree/main/.agents/skills/pnpm-audit-alert-issue
Command: npx skills add https://github.com/shoji9x9/skills --skill pnpm-audit-alert-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Dependabot currently cannot parse pnpm 11's multi-document pnpm-lock.yaml format, leaving pnpm projects without automated vulnerability alerts and forcing teams to manually track and create security issues for detected flaws.

Core Features & Use Cases

  • pnpm Audit Normalization: Converts raw pnpm audit JSON output into structured, consistent findings compatible with the dependabot-alert-issue skill's external audit mode.
  • Dependency Context Enrichment: Adds pnpm-specific dependency path details via pnpm why to help triage the impact and origin of each vulnerability.
  • Seamless Workflow Integration: Delegates duplicate checking, triage, and GitHub Issue creation to the existing dependabot-alert-issue skill to avoid redundant work and maintain consistent issue formatting.
  • Use Case: For teams using pnpm 11 with devEngines.packageManager configured, this skill ensures all vulnerabilities detected by pnpm audit are tracked as GitHub Issues even when Dependabot alerts are not generated.

Quick Start

Use the pnpm-audit-alert-issue skill to scan your pnpm 11 project for vulnerabilities and automatically create tracked GitHub Issues for all detected security flaws when Dependabot alerts are unavailable.

Frequently Asked Questions about pnpm-audit-alert-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track pnpm audit vulnerabilities when Dependabot fails to generate alerts?

To track pnpm audit vulnerabilities when Dependabot fails, you can normalize raw pnpm audit JSON output into structured findings and automatically create GitHub Issues to track detected security flaws.

Why does Dependabot not generate security alerts for pnpm 11 lockfiles?

Dependabot does not generate security alerts for pnpm 11 lockfiles because it currently cannot parse the multi-document pnpm-lock.yaml format, leaving projects without automated vulnerability tracking.

How do I get dependency path context for pnpm audit findings during triage?

To get dependency path context for pnpm audit findings during triage, you can enrich raw audit data with pnpm-specific dependency path details using pnpm why to identify the impact and origin of vulnerabilities.

Can I create GitHub issues from pnpm audit results without modifying existing Dependabot workflows?

Yes, you can create GitHub issues from pnpm audit results without modifying existing Dependabot workflows by delegating duplicate checking, triage, and issue drafting to an external audit findings integration mode.

Does this vulnerability tracking approach require devEngines.packageManager to be configured?

Yes, this vulnerability tracking approach requires devEngines.packageManager to be configured in your pnpm 11 project to accurately detect and track vulnerabilities as GitHub Issues when Dependabot alerts are unavailable.