alert

vcap_services

v0.7.1

Parse and return service credentials from VCAP_SERVICES.

Unknown
Latest version published 2 years ago
    npm install vcap_services
  

Package Health Score

53 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Recognized
Download trend

Weekly Downloads (22,432)

Dependents
15
GitHub Stars
0
Forks
10
Contributors
8

The npm package vcap_services receives a total of 22,432 downloads a week. As such, we scored vcap_services popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package vcap_services, we found that it has been starred ? times, and that 15 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.

Security

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

04/2017
07/2018
08/2018
10/2018
07/2019

Direct Vulnerabilities

Popular
0.3.4
  • 0
    H
  • 0
    M
  • 0
    L
0.4.0
  • 0
    H
  • 0
    M
  • 0
    L
0.5.1
  • 0
    H
  • 0
    M
  • 0
    L
0.6.0
  • 0
    H
  • 0
    M
  • 0
    L
0.7.1
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
0.3.4
  • 0
    H
  • 0
    M
  • 0
    L
0.4.0
  • 0
    H
  • 0
    M
  • 0
    L
0.5.1
  • 0
    H
  • 0
    M
  • 0
    L
0.6.0
  • 0
    H
  • 0
    M
  • 0
    L
0.7.1
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
0.3.4
  • 0
    H
  • 0
    M
  • 0
    L
0.4.0
  • 0
    H
  • 0
    M
  • 0
    L
0.5.1
  • 0
    H
  • 0
    M
  • 0
    L
0.6.0
  • 0
    H
  • 0
    M
  • 0
    L
0.7.1
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
Unknown
Alert

Unable to detect license

We couldn’t find an appropriate license for this project. It is highly advised to make sure the project license is compatible with your business needs before including it as a dependency, to keep yourself protected from infringement suits or loss of your own code.


Security Policy
No

We found a way for you to contribute to the project! Looks like vcap_services is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test vcap_services
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
0
Open PR
4
Last Release
2 years ago
Last Commit
12 months ago

Further analysis of the maintenance status of vcap_services 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 vcap_services 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.

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.

Community

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

This project has seen only 10 or less contributors.

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

How about a good first contribution to this project? It seems that vcap_services is missing a LICENSE file.


Embed Package Health Score Badge

package health: 53/100 package health 53/100

Package

Node.js Compatibility
not defined

Age
6 years
Dependencies
0 Direct
Versions
17
Install Size
13.5 kB
Dist-tags
1
# of Files
5
Maintainers
1
TS Typings
No

vcap_services 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.