Is @pb33f/openapi-changes safe to use?

@pb33f/openapi-changes has no known vulnerabilities on the latest version (0.2.6). DepScope rates its health at 77/100 (moderate risk).

What is the latest version of @pb33f/openapi-changes?

The latest version of @pb33f/openapi-changes is 0.2.6, released 2026-04-26.

No known vulnerabilities on the latest version of @pb33f/openapi-changes.

No, @pb33f/openapi-changes is actively maintained. Latest release: 0.2.6 (2026-04-26).

Popular alternatives to @pb33f/openapi-changes in npm include: minimatch, commander, eslint-visitor-keys, ajv, color-name.

@pb33f/openapi-changes is licensed under Apache-2.0.

npmv0.2.6

The world's sexiest and most detailed OpenAPI diff/changelog tool

License Apache-2.0permissive88 versions1 maintainers3 deps12,923 weekly dl

/ 100

Health

safe to use

@pb33f/[email protected] is safe to use (health: 77/100)

Health breakdown0 – 100

25/25

maintenance

10/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

🌟

0/10untyped

No type definitions available

Dependencies (3)

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@pb33f/openapi-changes