sku-for-testing

v10.3.7

Front-end development toolkit, powered by Webpack, Babel, CSS Modules, Less and Jest For more information about how to use this package see README

Latest version published 4 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

55 / 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
10.3.7 | 06/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
479
Forks
35
Contributors
40

Direct Usage Popularity


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

Based on project statistics from the GitHub repository for the npm package sku-for-testing, we found that it has been starred 479 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
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
40
Funding
No

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


Embed Package Health Score Badge

package health: 55/100 package health 55/100

Maintenance

Inactive

Commit Frequency

Open Issues
1
Open PR
3
Last Release
4 years ago
Last Commit
22 days ago

Further analysis of the maintenance status of sku-for-testing 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 sku-for-testing 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.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
>=10.13.0

Age
4 years
Dependencies
109 Direct
Versions
2
Install Size
274 kB
Dist-tags
1
# of Files
212
Maintainers
1
TS Typings
No

sku-for-testing 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.