Package Health Score

42 / 100

security
No known security issues
popularity
Limited
maintenance
Inactive
community
Limited

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
0.2.2	\|	05/2015	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.1.2	\|	05/2015		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

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

Limited

Weekly Downloads (570)

GitHub Stars: 0
Forks: 0
Contributors: 1

Direct Usage Popularity

The npm package readable-mock-req receives a total of 570 downloads a week. As such, we scored readable-mock-req popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package readable-mock-req, we found that it has been starred ? times.

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: 1
Funding: No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like readable-mock-req is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 0
Open PR: 0
Last Release: 10 years ago
Last Commit: 10 years ago

Further analysis of the maintenance status of readable-mock-req 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 readable-mock-req 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.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=0.10

Age: 10 years
Dependencies: 3 Direct
Versions: 7
Install Size: 0 B
Dist-tags: 1
# of Files: 0
Maintainers: 1
TS Typings: No

readable-mock-req 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.

Readme

http.IncomingMessage mock

Yet another http.IncomingMessage mock that is only a readable stream, not a writable stream. It tries to simulate IncomingMessage as close as possible by:

validating and setting uppercased method (defaults to GET),
ensuring there is a url (defaults to /),
populating headers and rawHeaders as expected,
populating trailers and rawTrailers after the end event,
ending the stream automatically when the method is GET/HEAD/DELETE.

Data can be piped into the request mock by either providing props.source (String, Buffer, Readable Stream), calling _setSource() with any of the aforementioned data types, or by using the usual suspects (_read(), read(), push(), unshift()).

Before passing through data from a source stream, the mock awaits the first read attempt, then periodically pulls as much as it can and as much the mock's buffer can handle, never more. Creating a mock and passing a source stream, then destroying the mock, creating another and setting the same source there without any actual read attempts will not cause any data to be pulled from the source.

Another mode of operation lets the mock consume data from the source stream immediately, effectively draining it. A callback can be used to be informed when all data has been transferred.

readable-mock-req supports Streams3 API via readable-stream ~v1.1.0.

Installation

npm install --save-dev readable-mock-req

API

new MockRequest(method, url, props)

Parameters:

Name	Type	Argument	Default	Description
`method`	string	<optional>	GET	HTTP method
`url`	url	<optional>	/	URL
`props`	object	<optional>	{}	Additional properties, like `headers` or `source`

Source:

readable-mock-req.js , lineno 142

_setSource(src, cb)

Set the source data or stream

Parameters:

Name	Type	Argument	Description
`src`	object \| string \| Buffer \| null		Source, stream or static data
`cb`	function \| boolean	<optional>	Pass true or a callback fn and all data from the source stream will be pulled upfront, having the Content-Length header set accordingly, if there is no such header already. Signature: `fn(err, length)`, where `err` is any potential Error as emitted by the source stream. `length` is provided in any case and shows how much data has been read.

Source:

readable-mock-req.js , lineno 214

setTimeout()

See http.IncomingMessage#setTimeout

Source:

readable-mock-req.js , lineno 201

generated with docme

Contributing

Take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using grunt test.

License

See LICENSE for more info.

readable-mock-req dependencies

is-readable-stream methods readable-stream

readable-mock-req development dependencies

chai format grunt grunt-coveralls grunt-eslint grunt-mocha-istanbul istanbul load-grunt-tasks mocha sinon

FAQs

What is readable-mock-req?

Yet another http.IncomingMessage mock (readable stream only). Visit Snyk Advisor to see a full health score report for readable-mock-req, including popularity, security, maintenance & community analysis.

Is readable-mock-req popular?

The npm package readable-mock-req receives a total of 570 weekly downloads. As such, readable-mock-req popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is readable-mock-req well maintained?

We found indications that readable-mock-req is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is readable-mock-req safe to use?

The npm package readable-mock-req was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 7 December-2024, at 21:45 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (570)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

http.IncomingMessage mock

Installation

API

new MockRequest(method, url, props)

Parameters:

_setSource(src, cb)

Parameters:

setTimeout()

Contributing

License

readable-mock-req dependencies

readable-mock-req development dependencies

FAQs

What is readable-mock-req?

Is readable-mock-req popular?

Is readable-mock-req well maintained?

Is readable-mock-req safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues