swagger-merger

v1.5.4

Merge multiple swagger files into a swagger file, support JSON/YAML. For more information about how to use this package see README

Latest version published 10 months ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

64 / 100

Security

No known security issues
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
1.5.4 | 02/2022
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.4.3 | 08/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.7.0 | 04/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.8.0 | 04/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.9.0 | 04/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Recognized

Weekly Downloads (16,347)

Download trend
Dependents
0
GitHub Stars
117
Forks
24
Contributors
7

Direct Usage Popularity

Occasionally

The npm package swagger-merger receives a total of 16,347 downloads a week. As such, we scored swagger-merger popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package swagger-merger, we found that it has been starred 117 times, and that 0 other projects in the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
7
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like swagger-merger is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 64/100 package health 64/100

Maintenance

Inactive

Commit Frequency

Open Issues
3
Open PR
2
Last Release
10 months ago
Last Commit
9 months ago

Further analysis of the maintenance status of swagger-merger based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

We found that swagger-merger demonstrates a positive version release cadence with at least one new version released in the past 12 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
>=12.22

Age
6 years
Dependencies
4 Direct
Versions
31
Install Size
26.3 kB
Dist-tags
1
# of Files
20
Maintainers
1
TS Typings
No

swagger-merger has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.