nodeify-fetch
Node streams for fetch
nodeify-fetch@3.1.0 was published on 2022-10-02. Its manifest declares 4 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All nodeify-fetch versions · Permanent reference to 3.1.0
Package specifications
| Version | 3.1.0 |
|---|---|
| License declaration | MIT |
| Published | 2022-10-02T15:30:40.865Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 4 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 20.66 KiB |
| Published file count | 26 |
| Package type | module |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 18 |
| Repository stars | 4 |
| Repository forks | 0 |
Install nodeify-fetch 3.1.0
npm install nodeify-fetch@3.1.0 pnpm add nodeify-fetch@3.1.0 yarn add nodeify-fetch@3.1.0
Runtime dependencies
- lodash ^4.17.21
- node-fetch ^3.2.10
- readable-stream ^4.2.0
- stream-chunks ^1.0.0
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- abort-controller@3.0.0 — indirect
- base64-js@1.5.1 — indirect
- buffer@6.0.3 — indirect
- data-uri-to-buffer@4.0.1 — indirect
- event-target-shim@5.0.1 — indirect
- events@3.3.0 — indirect
- fetch-blob@3.2.0 — indirect
- formdata-polyfill@4.0.10 — indirect
- ieee754@1.2.1 — indirect
- lodash@4.18.1 — direct
- node-domexception@1.0.0 — indirect
- node-fetch@3.3.2 — direct
- process@0.11.10 — indirect
- readable-stream@4.8.0 — direct
- safe-buffer@5.2.1 — indirect
- stream-chunks@1.0.0 — direct
- string_decoder@1.3.0 — indirect
- web-streams-polyfill@3.3.3 — indirect
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 6/10 — 8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6 |
|---|---|
| Code-Review | 0/10 — Found 0/2 approved changesets -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/nodeify-fetch/3.1.0 — retrieved 2026-10-29T12:44:32.908Z
- https://api.deps.dev/v3/systems/npm/packages/nodeify-fetch/versions/3.1.0 — retrieved 2026-10-29T12:44:33.447Z
- https://api.deps.dev/v3/systems/npm/packages/nodeify-fetch/versions/3.1.0:dependencies — retrieved 2026-10-29T12:44:33.481Z
- https://api.deps.dev/v3/projects/github.com%2Fbergos%2Fnodeify-fetch — retrieved 2026-10-29T12:44:33.608Z