stream-http 1.0.1
Streaming http in the browser
stream-http@1.0.1 was published on 2015-07-13. Its manifest declares 5 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 stream-http versions · Permanent reference to 1.0.1 · Latest release
Package specifications
| Version | 1.0.1 |
|---|---|
| License declaration | MIT |
| Published | 2015-07-13T01:43:57.627Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 5 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 5 |
| Repository stars | 356 |
| Repository forks | 63 |
Install stream-http 1.0.1
npm install stream-http@1.0.1 pnpm add stream-http@1.0.1 yarn add stream-http@1.0.1
Runtime dependencies
- builtin-status-codes ~1.0.0
- foreach ^2.0.5
- inherits ^2.0.1
- object-keys 1.0.4
- xtend ^4.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.
- builtin-status-codes@1.0.0 — direct
- foreach@2.0.6 — direct
- inherits@2.0.4 — direct
- object-keys@1.0.4 — direct
- xtend@4.0.2 — direct
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.
| Code-Review | 1/10 — Found 3/21 approved changesets -- score normalized to 1 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- 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 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/stream-http/1.0.1 — retrieved 2026-10-29T11:20:40.786Z
- https://api.deps.dev/v3/projects/github.com%2Fjhiesey%2Fstream-http — retrieved 2026-10-29T08:47:07.213Z
- https://api.deps.dev/v3/systems/npm/packages/stream-http/versions/1.0.1 — retrieved 2026-10-29T11:20:41.322Z
- https://api.deps.dev/v3/systems/npm/packages/stream-http/versions/1.0.1:dependencies — retrieved 2026-10-29T11:20:41.337Z