get

v1.4.0

A slightly higher-level HTTP client for node.

BSD-3-Clause
Latest version published 6 years ago
    npm install get
  

Package Health Score

54 / 100
  • Popularity
    Recognized
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Limited
Make sure the open source you're using is safe to use
Secure my Project

Popularity

Recognized
Weekly Downloads (32,755)
Dependents
25
GitHub Stars
16
Forks
10
Contributors
20

The npm package get receives a total of 32,755 downloads a week. As such, we scored get popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package get, we found that it has been starred 16 times, and that 25 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

Direct Vulnerabilities

0.2.1
0.3.0
0.4.2
1.3.0
1.4.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.2.1
0.3.0
0.4.2
1.3.0
1.4.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.2.1
0.3.0
0.4.2
1.3.0
1.4.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 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.

License
BSD-3-Clause

Security Policy
No

We found a way for you to contribute to the project! Looks like get 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.

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

    # Install the Snyk CLI and test your project
npm i snyk && snyk test get
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
0
Merged PR
12
Open PR
0
Last Commit
6 years ago

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

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

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


Embed Package Health Score Badge

package health: 54/100 package health 54/100

Package

Node.js Compatibility
>= 0.3.6

Age
10 years
Dependencies
0 Direct
Versions
23
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
6
TS Typings
No

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