primer-progress

v1.0.0

Use Progress components to visualize task completion

MIT
Latest version published 3 years ago
    npm install primer-progress
  

Package Health Score

69 / 100

Popularity

Small

Weekly Downloads (883)

Download trend
Dependents
46
GitHub Stars
10.49K
Forks
937
Contributors
130

Direct Usage Popularity


The npm package primer-progress receives a total of 883 downloads a week. As such, we scored primer-progress popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package primer-progress, we found that it has been starred 10,494 times, and that 46 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

01/2019
01/2019

Direct Vulnerabilities

Popular
0.1.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
0.1.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
0.1.3
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like primer-progress 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 primer-progress
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
15
Open PR
1
Last Release
3 years ago
Last Commit
6 days ago

Further analysis of the maintenance status of primer-progress 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 primer-progress 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
Yes
Code of Conduct
Yes
Contributors
130
Funding
No

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


Embed Package Health Score Badge

package health: 69/100 package health 69/100

Package

Node.js Compatibility
not defined

Age
3 years
Dependencies
1 Direct
Versions
254
Install Size
6.8 kB
Dist-tags
3
# of Files
8
Maintainers
1
TS Typings
No

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