1. Advisor
  2. JavaScript packages
  3. @expo/env

@expo/env

v0.4.0

hydrate environment variables from .env files into process.env For more information about how to use this package see README

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

81 / 100

Security

No known security issues
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
0.4.0 | 10/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.3.0 | 04/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.2.3 | 04/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.0 | 07/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.5 | 06/2023
  • 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 (755,467)

Download trend
GitHub Stars
34.34K
Forks
5.49K
Contributors
-

Direct Usage Popularity

TOP 30%

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

Based on project statistics from the GitHub repository for the npm package @expo/env, we found that it has been starred 34,341 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
No
Contributing.md
Yes
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 @expo/env is missing a Code of Conduct.

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

Embed Package Health Score Badge

package health: 81/100 package health 81/100

Maintenance

Healthy

Commit Frequency

Open Issues
421
Open PR
222
Last Release
2 months ago
Last Commit
1 month ago

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

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

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
2 years
Dependencies
5 Direct
Versions
58
Install Size
29.6 kB
Dist-tags
4
# of Files
9
Maintainers
27
TS Typings
No

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