1. Advisor
  2. JavaScript packages
  3. @chrisyang/core

@chrisyang/core

v3.0.0

Shared code for Jest test runner packages For more information about how to use this package see README

Latest version published 4 years ago
License: MIT
NPM
GitHub

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

48 / 100

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
3.0.0 | 12/2020
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
189
Forks
33
Contributors
20

Direct Usage Popularity

The npm package @chrisyang/core receives a total of 0 downloads a week. As such, we scored @chrisyang/core popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package @chrisyang/core, we found that it has been starred 189 times.

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

Community

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

With more than 10 contributors for the @chrisyang/core repository, this is possibly a sign for a growing and inviting community.

How about a good first contribution to this project? It seems that @chrisyang/core is missing a README file.

Embed Package Health Score Badge

package health: 48/100 package health 48/100

Maintenance

Inactive
archived

Commit Frequency

No Recent Commits
Open Issues
19
Open PR
8
Last Release
4 years ago
Last Commit
4 years ago

Further analysis of the maintenance status of @chrisyang/core 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 @chrisyang/core 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.

Keep your project healthy

scan-reversed

Check your package.json

NEW
Ensure all the packages you're using are healthy and well-maintained
arrow
intellij

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
not defined
Age
4 years
Dependencies
2 Direct
Versions
2
Install Size
27 kB
Dist-tags
1
# of Files
14
Maintainers
1
TS Typings
No

@chrisyang/core 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.