@availity/progress

v1.5.5

Availity progress bar For more information about how to use this package see README

Latest version published 1 month 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

79 / 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.5 | 02/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.4.1 | 06/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3.2 | 12/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.2.23 | 10/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.2.19 | 11/2020
Popular
  • 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 (52)

Download trend
GitHub Stars
49
Forks
30
Contributors
60

Direct Usage Popularity

Uncommon

The npm package @availity/progress receives a total of 52 downloads a week. As such, we scored @availity/progress popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package @availity/progress, we found that it has been starred 49 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
Yes
Code of Conduct
No
Contributors
60
Funding
No

With more than 10 contributors for the @availity/progress 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 @availity/progress is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 79/100 package health 79/100

Maintenance

Healthy

Commit Frequency

Open Issues
18
Open PR
13
Last Release
1 month ago
Last Commit
2 days ago

Further analysis of the maintenance status of @availity/progress based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @availity/progress demonstrates a positive version release cadence with at least one new version released in the past 3 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
not defined

Age
5 years
Dependencies
2 Direct
Versions
47
Install Size
20 kB
Dist-tags
2
# of Files
14
Maintainers
12
TS Typings
No

@availity/progress 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.