Homepage

expo-doctor vulnerabilities

Check your Expo project for known issues
Licenses: ISC | MIT
Published: 5 years ago Last updated: 2 days ago Latest version: 1.17.13 Latest non-vulnerable version: 1.18.0-canary-20251023-4c86f95
npm
GitHub

Package Health Score

89/100
  • securityNo known security issues
  • popularityInfluential project
  • maintenanceHealthy
  • communitySustainable

Maintenance

HEALTHY

Commit Frequency

Loading chart...

Open Issues
365
Open PR
448
New PRS
1
Last Release
2 days ago
Last Commit
2 days ago
Maintainers
11

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

We found that expo-doctor 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.

Popularity

INFLUENTIAL PROJECT
Weekly downloads (353.8k)
GitHub Stars
45.5k
Forks
10.2k
Contributors
0

The npm package expo-doctor receives a total of 353,762 downloads a week. As such, we scored expo-doctor popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package expo-doctor, we found that it has been starred 45,535 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
LICENSE
MIT

This project has seen only 10 or less contributors.

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

How about a good first contribution to this project? It seems that expo-doctor is missing a README file.

License

ISC
>=0.0.0 <0.0.1-canary-20231130-c8a9bf9;
MIT
>=0.0.1-canary-20231130-c8a9bf9;
Report a new vulnerability Found a mistake?

Direct Vulnerabilities

No direct vulnerabilities have been found for this package in Snyk’s vulnerability database. This does not include vulnerabilities belonging to this package’s dependencies.

Does your project rely on vulnerable package dependencies?

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities (in both your packages & their dependencies) and provides automated fixes for free.

Scan for indirect vulnerabilities

Security

NO KNOWN SECURITY ISSUES
Show only direct vulnerabilities in latest version
No vulnerabilities found

No vulnerabilities found in the latest version

Package versions

169 VERSIONS IN TOTAL See all versions
versionpublisheddirect vulnerabilities
1.18.0-canary-20251023-4c86f9523 Oct, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.18.0-canary-20251015-a6a127215 Oct, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.18.0-canary-20251013-623c5a613 Oct, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.18.0-canary-20251009-9919e089 Oct, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.17.14-canary-20251212-acb11f212 Dec, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.17.14-canary-20251211-7da85ea11 Dec, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.17.1311 Dec, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.17.13-canary-20251210-1f163e310 Dec, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.17.13-canary-20251206-615dec16 Dec, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.17.13-canary-20251205-a1dedc65 Dec, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

expo-doctor development dependencies

19 IN TOTAL
oraglobchalkdebuggetenvignoresemver@expo/env@expo/metro@vercel/ncc@expo/config@types/debugresolve-from@expo/schemerterminal-link@expo/json-file@expo/spawn-asyncexpo-module-scriptsresolve-workspace-root