@expo/config

v8.5.4

A library for interacting with the app.json For more information about how to use this package see README

Latest version published 2 months 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

83 / 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
8.5.4 | 01/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
8.4.0 | 10/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
7.0.3 | 10/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.0.26 | 07/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.0.9 | 08/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
Yes

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

Influential project

Weekly Downloads (867,617)

Download trend
GitHub Stars
28.44K
Forks
4.57K
Contributors
410

Direct Usage Popularity

TOP 5%

The npm package @expo/config receives a total of 867,617 downloads a week. As such, we scored @expo/config popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package @expo/config, we found that it has been starred 28,440 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
410
Funding
No

A good and healthy external contribution signal for @expo/config project, which invites more than one hundred open source maintainers to collaborate on the repository.

We found a way for you to contribute to the project! Looks like @expo/config is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 83/100 package health 83/100

Maintenance

Healthy

Commit Frequency

Open Issues
413
Open PR
258
Last Release
2 months ago
Last Commit
22 hours ago

Further analysis of the maintenance status of @expo/config based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @expo/config demonstrates a positive version release cadence with at least one new version released in the past 3 months.

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
not defined

Age
5 years
Dependencies
11 Direct
Versions
206
Install Size
153 kB
Dist-tags
4
# of Files
56
Maintainers
27
TS Typings
No

@expo/config 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.