Is @changesets/should-skip-package safe to use?

@changesets/should-skip-package has no known vulnerabilities on the latest version (0.1.2). DepScope rates its health at 64/100 (moderate risk).

What is the latest version of @changesets/should-skip-package?

The latest version of @changesets/should-skip-package is 0.1.2, released 2025-02-17.

Does @changesets/should-skip-package have known vulnerabilities?

No known vulnerabilities on the latest version of @changesets/should-skip-package.

Is @changesets/should-skip-package deprecated?

No, @changesets/should-skip-package is actively maintained. Latest release: 0.1.2 (2025-02-17).

What are alternatives to @changesets/should-skip-package?

Popular alternatives to @changesets/should-skip-package in npm include: semver, ansi-styles, debug, minimatch, brace-expansion.

What license does @changesets/should-skip-package use?

@changesets/should-skip-package is licensed under MIT.

@changesets/should-skip-package

npmv0.1.2

Checks if a package should be skipped for versioning or tagging purposes

License MITpermissive5 versions4 maintainers2 deps2,170,811 weekly dl

changesets/changesets.git#main

/ 100

Health

use with caution

@changesets/[email protected] low health (64/100) — consider alternatives

Moderate health score (64/100) — verify manually

Health breakdown0 – 100

5/25

maintenance

17/20

popularity

25/25

security

6/15

maturity

11/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (2)

@changesets/types @manypkg/get-packages

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@changesets/should-skip-package