content-type-parser

v1.0.2

Parse the value of the Content-Type header

MIT
Latest version published 4 years ago
    npm install content-type-parser
  

Package Health Score

38 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Popular

Weekly Downloads (441,564)

Download trend
Dependents
164
GitHub Stars
57
Forks
14
Contributors
4

Direct Usage Popularity

TOP 10%

The npm package content-type-parser receives a total of 441,564 downloads a week. As such, we scored content-type-parser popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package content-type-parser, we found that it has been starred 57 times, and that 164 other projects in the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Security

Security issues found
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

10/2017

Direct Vulnerabilities

Popular
1.0.2

Indirect Vulnerabilities

Popular
1.0.2
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
1.0.2
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like content-type-parser is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test content-type-parser
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
1
Open PR
1
Last Release
4 years ago
Last Commit
3 years ago

Further analysis of the maintenance status of content-type-parser 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 content-type-parser 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.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
4
Funding
Yes

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 38/100 package health 38/100

Package

Node.js Compatibility
not defined

Age
5 years
Dependencies
0 Direct
Versions
4
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

content-type-parser 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.