Is openapi-merge safe to use?

openapi-merge has no known vulnerabilities on the latest version (2.0.2). DepScope rates its health at 76/100 (moderate risk).

What is the latest version of openapi-merge?

The latest version of openapi-merge is 2.0.2, released 2026-08-08.

Does openapi-merge have known vulnerabilities?

No known vulnerabilities on the latest version of openapi-merge.

Is openapi-merge deprecated?

No, openapi-merge is actively maintained. Latest release: 2.0.2 (2026-08-08).

What are alternatives to openapi-merge?

Popular alternatives to openapi-merge in npm include: ?, semver, debug, minimatch.

What license does openapi-merge use?

openapi-merge is licensed under MIT.

openapi-merge

npmv2.0.2

A tool to merge numerous OpenAPI files into a single openapi definition.

License MITpermissive18 versions2 maintainers4 deps284,752 weekly dl

robertmassaioli/openapi-merge

/ 100

Health

safe to use

[email protected] is safe to use (health: 76/100)

Health breakdown0 – 100

20/25

maintenance

14/20

popularity

25/25

security

12/15

maturity

5/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (4)

@atlassian/atlassian-openapi jsonpointer lodash ts-is-present

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/openapi-merge