npmpackage.info

Gathering detailed insights and metrics for http-parser-js

Other packages similar to http-parser-js

@browsery/http-parser

0.5.9-r4

Browser compatible http-parser-js module

fast-xml-parser

4.5.0

Validate XML, Parse XML, Build XML without C/C++ based libraries

yargs-parser

21.1.1

the mighty option parser used by yargs

error-stack-parser

2.1.4

Extract meaning from JS Errors

Gathering detailed insights and metrics for http-parser-js

http-parser-js

A pure JS HTTP parser for node.

0.5.8

242

NOASSERTION

JavaScript

3,322,606,193 3.9

Installations

npm install http-parser-js

Score

100

Supply Chain

80.5

Quality

78.3

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

0

Total

49

Closed

10

Merged

39

Issues

Open

5

Total

48

Closed

43

Releases

Unable to fetch releases

Developer

creationix

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

Yes

Node Version

16.13.0

NPM Version

8.1.0 Statistics

242 Stars

154 Commits

58 Forks

10 Watching

9 Branches

18 Contributors

Updated on 18 Nov 2024

Languages

JavaScript (85.08%)

Python (14.92%)

Total Downloads

Cumulative downloads

Total Downloads

3,322,606,193

Last day

-3.7%

3,011,956

Compared to previous day

Last week

2.7%

15,958,154

Compared to previous week

Last month

13.5%

66,011,562

Compared to previous month

Last year

1.6%

720,034,930

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

No dependencies detected.

Versions

HTTP Parser

This library parses HTTP protocol for requests and responses. It was created to replace http_parser.c since calling C++ functions from JS is really slow in V8. However, it is now primarily useful in having a more flexible/tolerant HTTP parser when dealing with legacy services that do not meet the strict HTTP parsing rules Node's parser follows.

This is packaged as a standalone npm module. To use in node, monkeypatch HTTPParser.

1// Monkey patch before you require http for the first time.
2process.binding('http_parser').HTTPParser = require('http-parser-js').HTTPParser;
3
4var http = require('http');
5// ...

Testing

Simply run npm test. The tests are copied from node and mscedex/io.js, with some modifcations.

Status

This should now be usable in any node application, it now supports (nearly) everything http_parser.c does while still being tolerant with corrupted headers, and other kinds of malformed data.

Node versions

http-parser-js should work via monkey-patching on Node v6-v11, and v13-14.

Node v12.x renamed the internal http parser, and did not expose it for monkey-patching, so to be able to monkey-patch on Node v12, you must run node --http-parser=legacy file.js to opt in to the old, monkey-patchable http_parser binding.

Standalone usage

While this module is intended to be used as a replacement for the internal Node.js parser, it can be used as a standalone parser. The standalone-example.js demonstrates how to use the somewhat awkward API (coming from compatibility with the Node.js internals) to parse HTTP from raw Buffers.

License

MIT. See LICENSE.md

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

9

License

Determines if the project has defined a license.

5

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

3.9

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More