read

v1.0.7

read(1) for node programs

ISC
Latest version published about 5 years ago
    npm install read
  

Package Health Score

58 / 100
  • Popularity
    Influential project
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Sustainable

Popularity

Influential project
Weekly Downloads (3,114,714)
Dependents
807
GitHub Stars
164
Forks
33
Contributors
4

The npm package read receives a total of 3,114,714 downloads a week. As such, we scored read popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package read, we found that it has been starred 164 times, and that 807 other projects on 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

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

0.0.3
0.1.1
1.0.7
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.3
0.1.1
1.0.7
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.0.3
0.1.1
1.0.7
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security Policy
No

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

We found a way for you to contribute to the project! Looks like read is missing a security policy.

    # Install the Snyk CLI and test your project
npm i snyk && snyk test read
Fix it in your project with Snyk!

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
11
Merged PR
0
Open PR
5
Last Commit
5 years ago

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

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
4
Funding
No
License
ISC

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 58/100 package health 58/100

Package

Node.js Compatibility
>=0.8

Age
9 years
Dependencies
1 Direct / 1 Total
Versions
3
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
Yes

We detected a total of 1 direct & transitive dependencies for read. See the full dependency tree of read

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