← Explore all skills

PACKAGE MANAGER AUDITING / Grafana

npm supply-chain audit

Pins Grafana's package-manager audit, which is read-only, stops when package.json is missing, and stops again when every check passes.

“Audit a JavaScript/TypeScript repo's npm, yarn, or pnpm configuration for supply-chain hardening: tool version, lifecycle scripts, unsafe dependency protocols, and minimum release age ≥3 days. …”

01 / THE REASONING

Why this made the selection.

  • No selected skills record uses this source path.
  • The file is a read-only audit that says not to modify files, and it stops when the workspace root has no package.json.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • skills/grafana-plugins/check-npm/SKILL.md
  • README.md
  • LICENSE

Our findings

  • The audit is read-only and says not to modify any files.
  • A missing root package.json is a stop, before the later checks.
  • Script policy, dependency protocols, and minimum release age are separate pass or fail checks, with different floors for npm, yarn, and pnpm 10 versus 11.
  • When every check passes, the skill says to report that and stop.
  • A failure is reported with a fix snippet. The file does not say to write that snippet into the repo.
  • Dependency-protocol scanning first discovers workspace members; the recursive fallback is explicitly identified as capable of matching manifests outside the workspace.

Not established by this review

  • The resource was not executed and its tools were not called.
  • npm, yarn, and pnpm were not run.
  • No .npmrc, .yarnrc.yml, pnpm-workspace.yaml, or package.json was modified.
  • The reference files under references/ were not opened.
  • Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Add a skill to your workflow.

Upstream setup instructions ↗

DOCUMENTED COMMAND

claude plugin install grafana-plugins@grafana-skills

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. The root README Claude Code section shows claude plugin marketplace add grafana/skills and then claude plugin install grafana-plugins@grafana-skills.
  2. That command installs the grafana-plugins plugin group. It does not install this file alone.
  3. The same README shows npx skills add grafana/skills for the repository. Its single-skill flag is demonstrated only for frontend-session-rca.
  4. This review did not run either install.

Before you start

  • Claude Code if the plugin command is used
  • A JavaScript workspace only if the audit steps are followed, which this review did not run

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. check-npm SKILL.md ↗Checked

    https://github.com/grafana/skills/blob/1ccacf29049fde66637fe01ab93a83a772da323b/skills/grafana-plugins/check-npm/SKILL.md

    Supports: read-only rule, missing package.json stop, and stop when every check passes

  2. Repository README ↗Checked

    https://github.com/grafana/skills/blob/1ccacf29049fde66637fe01ab93a83a772da323b/README.md

    Supports: Apache License 2.0 statement and plugin-group install line

  3. Repository LICENSE ↗Checked

    https://github.com/grafana/skills/blob/1ccacf29049fde66637fe01ab93a83a772da323b/LICENSE

    Supports: Apache License 2.0

  4. https://raw.githubusercontent.com/grafana/skills/1ccacf29049fde66637fe01ab93a83a772da323b/skills/grafana-plugins/check-npm/SKILL.md

    Supports: review.findings, bestFor, upstreamDescription

Evidence & Ask