expo-processing

v2.3.7

Utilities for using Processing.js on Expo For more information about how to use this package see README

Latest version published 5 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

84 / 100

Explore Similar Packages

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
2.3.7 | 04/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.2.4 | 05/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.3 | 11/2017
  • 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

Small

Weekly Downloads (71)

Download trend
GitHub Stars
33.21K
Forks
5.3K
Contributors
410

Direct Usage Popularity

TOP 30%

The npm package expo-processing receives a total of 71 downloads a week. As such, we scored expo-processing popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package expo-processing, we found that it has been starred 33,209 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
No
Contributing.md
Yes
Code of Conduct
No
Contributors
410
Funding
No

A good and healthy external contribution signal for expo-processing 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-processing is missing a Code of Conduct.

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


Embed Package Health Score Badge

package health: 84/100 package health 84/100

Maintenance

Healthy

Commit Frequency

Open Issues
415
Open PR
263
Last Release
5 months ago
Last Commit
9 hours ago

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

We found that expo-processing demonstrates a positive version release cadence with at least one new version released in the past 12 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
7 years
Dependencies
1 Direct
Versions
62
Install Size
5.37 kB
Dist-tags
4
# of Files
3
Maintainers
27
TS Typings
No

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