fstream 0.1.11
Advanced file system stream things
fstream@0.1.11 was published on 2012-01-05. Its manifest declares 4 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is 0.5 || 0.6 || 0.7.
Deprecated: This package is no longer supported.
All fstream versions · Permanent reference to 0.1.11 · Latest release
Package specifications
| Version | 0.1.11 |
|---|---|
| License declaration | Not declared |
| Published | 2012-01-05T00:47:21.323Z |
| Node.js requirement | 0.5 || 0.6 || 0.7 |
| 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 | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | fstream.js |
| Side effects declaration | Not declared |
| Direct advisories | 1 |
| Resolved graph dependencies | 4 |
| Repository stars | 209 |
| Repository forks | 51 |
Install fstream 0.1.11
npm install fstream@0.1.11 pnpm add fstream@0.1.11 yarn add fstream@0.1.11
Runtime dependencies
- mkdirp ~0.1.0
- rimraf ~1.0.8
- inherits ~1.0.0
- graceful-fs ~1.1.2
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.
- graceful-fs@1.1.14 — direct
- inherits@1.0.2 — direct
- mkdirp@0.1.0 — direct
- rimraf@1.0.9 — 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.
Known direct advisories
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 0/10 — project is archived |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 0/10 — Found 2/30 approved changesets -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge 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 |
| Security-Policy | 0/10 — security policy file not detected |
Evidence and freshness
- https://registry.npmjs.org/fstream/0.1.11 — retrieved 2026-10-29T12:13:40.001Z
- https://api.deps.dev/v3/projects/github.com%2Fnpm%2Ffstream — retrieved 2026-10-29T10:58:29.968Z
- https://api.deps.dev/v3/systems/npm/packages/fstream/versions/0.1.11 — retrieved 2026-10-29T12:13:40.500Z
- https://api.deps.dev/v3/systems/npm/packages/fstream/versions/0.1.11:dependencies — retrieved 2026-10-29T12:13:40.527Z