1. Advisor
  2. JavaScript packages
  3. bible-reference-range

bible-reference-range

v1.1.1

[![CI Status](https://github.com/unfoldingWord/bible-reference-range/workflows/CI/badge.svg)](https://github.com/unfoldingWord/bible-reference-range/actions) [![Current Verison](https://img.shields.io/github/tag/unfoldingWord/bible-reference-range.svg)](h For more information about how to use this package see README

Latest version published 12 months ago
License: MIT
NPM
GitHub

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

62 / 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.1.1 | 12/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.1 | 07/2022
  • 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

Limited

Weekly Downloads (75)

Download trend
GitHub Stars
0
Forks
3
Contributors
20

Direct Usage Popularity

The npm package bible-reference-range receives a total of 75 downloads a week. As such, we scored bible-reference-range popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package bible-reference-range, we found that it has been starred ? times.

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

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
20
Funding
No

With more than 10 contributors for the bible-reference-range 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 bible-reference-range is missing a Code of Conduct.

Embed Package Health Score Badge

package health: 62/100 package health 62/100

Maintenance

Sustainable

Commit Frequency

Open Issues
7
Open PR
2
Last Release
12 months ago
Last Commit
6 months ago

Further analysis of the maintenance status of bible-reference-range based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

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

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

Keep your project healthy

scan-reversed

Check your package.json

NEW
Ensure all the packages you're using are healthy and well-maintained
arrow
intellij

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
not defined
Age
2 years
Dependencies
0 Direct
Versions
7
Install Size
171 kB
Dist-tags
1
# of Files
15
Maintainers
11
TS Typings
No

bible-reference-range 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.