code-rechecking

v1.0.0

在开发的过程中我们往往会存在大量的复制粘贴代码的行为,这一点在项目的开发初期尤其显著;而在项目逐步稳定,功能需求逐步完善之后我们就需要考虑对代码库的优化与重构,尽量编写清晰可维护的代码。好的代码往往是在合理范围内尽可能地避免重复代码,遵循单一职责与 Single Source of Truth 等原则。 For more information about how to use this package see README

Latest version published 5 years ago
License: MIT

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

39 / 100

Explore Similar Packages

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
1.0.0 | 12/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 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.

Get started free

Popularity

Limited

Weekly Downloads (0)

Download trend
GitHub Stars
80
Forks
5
Contributors
-

Direct Usage Popularity


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

Based on project statistics from the GitHub repository for the npm package code-rechecking, we found that it has been starred 80 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
0
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-rechecking is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 39/100 package health 39/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
2
Open PR
0
Last Release
5 years ago
Last Commit
3 years ago

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

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