content-type-parser

v1.0.2

Parse the value of the Content-Type header

MIT
Latest version published 5 years ago
    npm install content-type-parser
  
We couldn't find any similar packages Browse all packages

Package Health Score

35 / 100

Security

Security issues found
Powered by Snyk
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.0.2 | 10/2017
Popular
  • 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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test content-type-parser
Get started free

Popularity

Popular

Weekly Downloads (441,911)

Download trend
Dependents
164
GitHub Stars
60
Forks
16
Contributors
4

Direct Usage Popularity

TOP 30%

The npm package content-type-parser receives a total of 441,911 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 60 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.

Community

Limited
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: 35/100 package health 35/100

Maintenance

Inactive

Commit Frequency

Open Issues
0
Open PR
2
Last Release
5 years ago
Last Commit
11 months 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.

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
not defined

Age
6 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.