valhalla

v3.0.0-rc.4

While Valhalla on v3.0 is under development, we recommend that you use the last stable release, [2.6.1](https://github.com/valhalla/valhalla/releases/tag/2.6.1) until further notice.

ISC
Latest version published 3 years ago
    npm install valhalla
  

Package Health Score

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

Popularity

Limited
Download trend

Weekly Downloads (17)

Dependents
0
GitHub Stars
1.46K
Forks
313
Contributors
130

The npm package valhalla receives a total of 17 downloads a week. As such, we scored valhalla popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package valhalla, we found that it has been starred 1,456 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.

Security

Security review needed
Powered by Snyk

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

0.0.2
3.0.0-rc.4
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.2
3.0.0-rc.4
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.0.2
3.0.0-rc.4
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
ISC

Security Policy
No

We found a way for you to contribute to the project! Looks like valhalla 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 valhalla
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

Open Issues
456
Open PR
45
Last Release
3 years ago
Last Commit
13 days ago

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

Active
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
130
Funding
No

A good and healthy external contribution signal for valhalla project, which invites more than one hundred open source maintainers to collaborate on the repository.

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


Embed Package Health Score Badge

package health: 58/100 package health 58/100

Package

Node.js Compatibility
>=8.11.2

Age
5 years
Dependencies
3 Direct
Versions
8
Install Size
224 kB
Dist-tags
2
# of Files
9
Maintainers
8
TS Typings
No

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