cve-report

Report which CVEs were fixed in each Questarr release by diffing package-lock.json across version tags and checking OSV.dev

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/Doezer/Questarr --skill cve-report

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

name	cve-report
description	Report which CVEs were fixed in each Questarr release by diffing package-lock.json across version tags and checking OSV.dev
disable-model-invocation	false

If the user asked about the full release history, run node scripts/cve-report.mjs (no args) — it walks every consecutive v* tag boundary plus the unreleased range from the latest tag to HEAD, diffing resolved package-lock.json versions (direct and transitive) and checking OSV.dev for CVEs fixed by each bump.
If the user asked about a specific version or range, run node scripts/cve-report.mjs <fromTag> <toTag> for just that boundary instead. List tags first with git tag --list 'v*' --sort=v:refname if the exact tag names aren't already known.
Present the script's output to the user as-is — it is already grouped per version boundary, then by scope (Production/Development dependencies) and severity (CRITICAL → HIGH → MODERATE → LOW → UNKNOWN) within each. Do not add, infer, or embellish CVE claims beyond what the script printed; OSV.dev is the source of truth here.
If the user wants the report saved, write it to docs/CVE-REPORT.md (or a path they specify). Do not auto-edit docs/CHANGELOG.md — CVE attribution needs human review before it becomes part of published release notes.
If the script errors (network failure reaching OSV.dev, a ref missing package-lock.json, etc.), report the specific error to the user rather than retrying blindly or guessing at results.