meros

v1.3.0

A fast 642B utility that makes reading multipart responses simple 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

70 / 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
1.3.0 | 05/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.2.1 | 09/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.3 | 10/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

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 (3,227,686)

Download trend
GitHub Stars
187
Forks
10
Contributors
-

Direct Usage Popularity

TOP 30%

The npm package meros receives a total of 3,227,686 downloads a week. As such, we scored meros popularity level to be Influential project.

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

This project has seen only 10 or less contributors.


Embed Package Health Score Badge

package health: 70/100 package health 70/100

Maintenance

Inactive

Commit Frequency

Open Issues
1
Open PR
0
Last Release
1 year ago
Last Commit
10 months ago

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

An important project maintenance signal to consider for meros 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.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
>=13

Age
4 years
Dependencies
0 Direct
Versions
30
Install Size
15.3 kB
Dist-tags
3
# of Files
10
Maintainers
1
TS Typings
No

meros 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.