formstream 0.0.7
A multipart/form-data encoded stream, helper for file upload.
formstream@0.0.7 was published on 2013-07-25. 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 formstream versions · Permanent reference to 0.0.7 · Latest release
Package specifications
| Version | 0.0.7 |
|---|---|
| License declaration | MIT |
| Published | 2013-07-25T14:38:11.584Z |
| 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 | 4 |
| Repository stars | 144 |
| Repository forks | 19 |
Install formstream 0.0.7
npm install formstream@0.0.7 pnpm add formstream@0.0.7 yarn add formstream@0.0.7
Runtime dependencies
- mime 1.2.9
- pause-stream >=0.0.10
- buffer-concat 0.0.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.
- buffer-concat@0.0.1 — direct
- mime@1.2.9 — direct
- pause-stream@0.0.11 — direct
- through@2.3.8 — 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.
| Code-Review | 1/10 — Found 4/30 approved changesets -- score normalized to 1 |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| 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 |
| Security-Policy | 0/10 — security policy file not detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/formstream/0.0.7 — retrieved 2026-10-31T21:51:25.048Z
- https://api.deps.dev/v3/systems/npm/packages/formstream/versions/0.0.7 — retrieved 2026-10-31T21:51:25.454Z
- https://api.deps.dev/v3/systems/npm/packages/formstream/versions/0.0.7:dependencies — retrieved 2026-10-31T21:51:25.480Z
- https://api.deps.dev/v3/projects/github.com%2Fnode-modules%2Fformstream — retrieved 2026-10-29T12:02:52.212Z (stale snapshot; refresh pending)