strider

v2.4.20

Brilliant continuous deployment platform For more information about how to use this package see README

Latest version published 4 years ago
License: BSD-3-Clause

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

51 / 100

Security

Security review needed
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
2.4.20 | 08/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.3.0 | 04/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.11.0 | 08/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.10.1 | 07/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.9.6 | 03/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
BSD-3-Clause
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

Small

Weekly Downloads (7)

Download trend
GitHub Stars
4.6K
Forks
431
Contributors
-

Direct Usage Popularity


The npm package strider receives a total of 7 downloads a week. As such, we scored strider popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package strider, we found that it has been starred 4,600 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
Yes
Contributors
0
Funding
Yes

This project has seen only 10 or less contributors.


Embed Package Health Score Badge

package health: 51/100 package health 51/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
177
Open PR
4
Last Release
4 years ago
Last Commit
3 years ago

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

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

Package

Node.js Compatibility
>=10.13.0 || >=11.10.1

Age
12 years
Dependencies
76 Direct
Versions
94
Install Size
21.8 MB
Dist-tags
2
# of Files
344
Maintainers
3
TS Typings
No

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