yapi-verndor

v1.4.1

YAPI For more information about how to use this package see README

Latest version published 6 years ago
License: Apache-2.0

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

45 / 100

Explore Similar Packages

Security

Security review needed
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.4.1 | 11/2018
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Apache-2.0
Security Policy
Yes

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

Small

Weekly Downloads (0)

Download trend
GitHub Stars
27.35K
Forks
4.78K
Contributors
80

Direct Usage Popularity


The npm package yapi-verndor receives a total of 0 downloads a week. As such, we scored yapi-verndor popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package yapi-verndor, we found that it has been starred 27,354 times.

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
80
Funding
No

With more than 10 contributors for the yapi-verndor repository, this is possibly a sign for a growing and inviting community.

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


Embed Package Health Score Badge

package health: 45/100 package health 45/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
1.52K
Open PR
77
Last Release
6 years ago
Last Commit
2 years ago

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

An important project maintenance signal to consider for yapi-verndor is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
>= 7.6.0

Age
6 years
Dependencies
49 Direct
Versions
2
Install Size
52.3 MB
Dist-tags
1
# of Files
331
Maintainers
1
TS Typings
No

yapi-verndor 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.