npm package
Home@changesets/should-skip-package
The @changesets/should-skip-package package checks if a package should be skipped for versioning or tagging purposes. It is useful in managing versioning and changelogs, particularly in monorepo setups. This tool helps maintain consistency and organization in package updates.
- lurq health score
- 87/100
- Confidence
- proven
- Weekly downloads
- 3,937,375
- Latest version
- 1.0.0
- Last release
- Aug 19, 2026
- License
- MIT
Should you depend on @changesets/should-skip-package?
lurq's verdict: low
- No known advisories
Check this from your coding agent
This page is a daily snapshot. lurq's verify tool checks @changesets/should-skip-package at the exact version your agent is about to install, and compat checks it against the rest of your stack. One command connects Claude Code, Cursor, VS Code and other agents:
npx lurqrun
Free to start. Quickstart
Other utility packages lurq scores
- dompurify98/100 · proven
- pdfjs-dist95/100 · proven
- @puppeteer/browsers94/100 · proven
- puppeteer-core94/100 · proven
- puppeteer94/100 · proven
Scored from public signals (npm registry, GitHub, deps.dev and advisory databases). Data as of Sep 1, 2026; this page refreshes every 24 hours. Source repository.