Is openapi-merge safe to use?

openapi-merge has no known vulnerabilities on the latest version (1.3.3). DepScope rates its health at 59/100 (high risk).

What is the latest version of openapi-merge?

The latest version of openapi-merge is 1.3.3, released 2024-06-06.

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: 1.3.3 (2024-06-06).

What are alternatives to openapi-merge?

Popular alternatives to openapi-merge in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does openapi-merge use?

openapi-merge is licensed under MIT.

openapi-merge

npmv1.3.3

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

License MITpermissive17 versions2 maintainers3 deps385,306 weekly dl

robertmassaioli/openapi-merge

/ 100

Health

use with caution

[email protected] low health (59/100) — consider alternatives

Moderate health score (59/100) — verify manually

Health breakdown0 – 100

5/25

maintenance

14/20

popularity

25/25

security

12/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (3)

atlassian-openapi lodash ts-is-present

API access

Get this data programmatically — free, no authentication.

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