code-recheck

v1.1.2

一键查重,自动检查项目中的重复代码

MIT
Latest version published 3 years ago
    npm install code-recheck
  

Package Health Score

39 / 100

Security

Security review needed
Powered by Snyk
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
1.1.2 | 12/2019
Popular
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0 | 12/2019
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test code-recheck
Get started free

Popularity

Limited

Weekly Downloads (5)

Download trend
Dependents
0
GitHub Stars
70
Forks
3
Contributors
2

Direct Usage Popularity


The npm package code-recheck receives a total of 5 downloads a week. As such, we scored code-recheck popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package code-recheck, we found that it has been starred 70 times, and that 0 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.

Community

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

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 39/100 package health 39/100

Maintenance

Inactive

Commit Frequency

Open Issues
2
Open PR
0
Last Release
3 years ago
Last Commit
8 months ago

Further analysis of the maintenance status of code-recheck 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 code-recheck 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
3 years
Dependencies
2 Direct
Versions
5
Install Size
68.8 kB
Dist-tags
1
# of Files
11
Maintainers
1
TS Typings
No

code-recheck 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.