progress-stream 1.1.0
Read the progress of a stream
progress-stream@1.1.0 was published on 2015-04-01. Its manifest declares 3 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 progress-stream versions · Permanent reference to 1.1.0 · Latest release
Package specifications
| Version | 1.1.0 |
|---|---|
| License declaration | BSD-2-Clause |
| Published | 2015-04-01T20:09:17.682Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| 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 | 10 |
| Repository stars | 234 |
| Repository forks | 31 |
Install progress-stream 1.1.0
npm install progress-stream@1.1.0 pnpm add progress-stream@1.1.0 yarn add progress-stream@1.1.0
Runtime dependencies
- through2 ~0.2.3
- speedometer ~0.1.2
- single-line-log ~0.3.1
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.
- core-util-is@1.0.3 — indirect
- inherits@2.0.4 — indirect
- isarray@0.0.1 — indirect
- object-keys@0.4.0 — indirect
- readable-stream@1.1.14 — indirect
- single-line-log@0.3.1 — direct
- speedometer@0.1.4 — direct
- string_decoder@0.10.31 — indirect
- through2@0.2.3 — direct
- xtend@2.1.2 — 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.
| 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 |
| Code-Review | 2/10 — Found 7/29 approved changesets -- score normalized to 2 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Security-Policy | 0/10 — security policy file not detected |
| 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/progress-stream/1.1.0 — retrieved 2026-10-29T10:50:10.123Z
- https://api.deps.dev/v3/projects/github.com%2Ffreeall%2Fprogress-stream — retrieved 2026-10-29T07:15:00.768Z
- https://api.deps.dev/v3/systems/npm/packages/progress-stream/versions/1.1.0 — retrieved 2026-10-29T10:50:10.639Z
- https://api.deps.dev/v3/systems/npm/packages/progress-stream/versions/1.1.0:dependencies — retrieved 2026-10-29T10:50:10.675Z