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

@frida/http-parser-js

1.0.0

A pure JS HTTP parser for Frida

@achingbrain/http-parser-js

0.5.9

A pure JS HTTP parser

url-js

2.1.0

Simple URL parser, similar to DOM URL

Gathering detailed insights and metrics for http-parser-js

http-parser-js - 0.5.10 | npmpackage.info

http-parser-js

A pure JS HTTP parser for node.

0.5.10

245

NOASSERTION

JavaScript

2.36 kB

3,735,356,601 4

Installations

npm install http-parser-js

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Node Version

22.12.0

NPM Version

10.9.0 Pull Requests

Open

1

Total

54

Closed

11

Merged

42

Issues

Open

5

Total

48

Closed

43

Releases

Unable to fetch releases

Languages

JavaScript

Python

JavaScript (85.1%)

Python (14.9%)

Developer

creationix

Download Statistics

Total Downloads

3,735,356,601

Last Day

850,158

Last Week

16,820,312

Last Month

73,312,359

Last Year

774,046,748

GitHub Statistics

NOASSERTION License

245 Stars

158 Commits

59 Forks

9 Watchers

9 Branches

20 Contributors

Updated on Apr 27, 2025

Bundle Size

6.68 kB

Minified

2.36 kB

Minified + Gzipped

Bundlephobia

Maintainers

View All 20 Contributors

Package Meta Information

Latest Version

0.5.10

Package Id

http-parser-js@0.5.10

Unpacked Size

25.85 kB

Size

7.54 kB

File Count

NPM Version

10.9.0

Node Version

22.12.0

Published on

Apr 08, 2025

Total Downloads

Cumulative downloads

Total Downloads

3,735,356,601

Last Day

-9.1%

850,158

Compared to previous day

Last Week

-9%

16,820,312

Compared to previous week

Last Month

1.9%

73,312,359

Compared to previous month

Last Year

9.9%

774,046,748

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

No dependencies detected.

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.

1

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

4

/10

Last Scanned on 2025-06-30

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