expo-permissions

v14.4.0

Allows you prompt for various permissions to access device sensors, personal data, etc. For more information about how to use this package see README

Latest version published 1 year 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

78 / 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
14.4.0 | 09/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
14.3.0 | 07/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
13.2.0 | 04/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
12.1.1 | 06/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
10.0.0 | 11/2020
Popular
  • 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

Popular

Weekly Downloads (18,113)

Download trend
GitHub Stars
34.47K
Forks
5.52K
Contributors
410

Direct Usage Popularity

TOP 5%

The npm package expo-permissions receives a total of 18,113 downloads a week. As such, we scored expo-permissions popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package expo-permissions, we found that it has been starred 34,466 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-permissions 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-permissions is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 78/100 package health 78/100

Maintenance

Sustainable

Commit Frequency

Open Issues
426
Open PR
234
Last Release
1 year ago
Last Commit
3 days ago

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

An important project maintenance signal to consider for expo-permissions 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
not defined

Age
6 years
Dependencies
0 Direct
Versions
59
Install Size
130 kB
Dist-tags
1
# of Files
59
Maintainers
33
TS Typings
Yes

expo-permissions 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.