connect-multiparty 1.0.0

multipart parsing middleware for connect using multiparty

connect-multiparty@1.0.0 was published on 2013-10-25. Its manifest declares 2 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.

Deprecated: This package is archived and no longer maintained. For support, visit https://github.com/expressjs/express/discussions

All connect-multiparty versions · Permanent reference to 1.0.0 · Latest release

Package specifications

Version1.0.0
License declarationMIT
Published2013-10-25T18:54:21.624Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories1
Resolved graph dependencies8
Repository stars349
Repository forks50

Install connect-multiparty 1.0.0

npm install connect-multiparty@1.0.0
pnpm add connect-multiparty@1.0.0
yarn add connect-multiparty@1.0.0

Runtime dependencies

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.

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.

Binary-Artifacts10/10 — no binaries found in the repo
Maintained0/10 — project is archived
Code-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
SAST0/10 — no SAST tool detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy10/10 — security policy file detected

Evidence and freshness