craco-up

v3.3.3

Create React App Configuration Override, an easy and comprehensible configuration layer for create-react-app v2. For more information about how to use this package see README

Latest version published 6 years ago
License: Apache-2.0

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

45 / 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.3.3 | 01/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Apache-2.0
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

Small

Weekly Downloads (0)

Download trend
GitHub Stars
7.44K
Forks
499
Contributors
70

Direct Usage Popularity


The npm package craco-up receives a total of 0 downloads a week. As such, we scored craco-up popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package craco-up, we found that it has been starred 7,439 times.

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

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
70
Funding
Yes

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


Embed Package Health Score Badge

package health: 45/100 package health 45/100

Maintenance

Inactive

Commit Frequency

Open Issues
45
Open PR
3
Last Release
6 years ago
Last Commit
12 months ago

Further analysis of the maintenance status of craco-up 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 craco-up 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
>=6

Age
6 years
Dependencies
3 Direct
Versions
5
Install Size
80.6 kB
Dist-tags
1
# of Files
30
Maintainers
1
TS Typings
No

craco-up 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.