requet

v0.0.1-security

security holding package For more information about how to use this package see README

Latest version published 6 years ago
License: Unknown

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

This is a malicious package

When installed through a typosquatting attack, the package will extract and upload information to a remote server including name of the downloaded package, name of the intended package, the Node version and whether the process was running as sudo.

Security

Security issues found
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
0.0.1-security | 04/2019
Popular
  • 0
    H
  • 0
    M
  • 0
    L
License
Unknown
Alert

Unable to detect license

We couldn’t find an appropriate license for this project. It is highly advised to make sure the project license is compatible with your business needs before including it as a dependency, to keep yourself protected from infringement suits or loss of your own code.

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 (3)

Download trend
GitHub Stars
157
Forks
58
Contributors
5

Direct Usage Popularity


The npm package requet receives a total of 3 downloads a week. As such, we scored requet popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package requet, we found that it has been starred 157 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

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

This project has seen only 10 or less contributors.

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

How about a good first contribution to this project? It seems that requet is missing a LICENSE file.


Embed Package Health Score Badge

package health: 21/100 package health 21/100

Maintenance

Inactive

Commit Frequency

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

Further analysis of the maintenance status of requet 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 requet 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
not defined

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

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