Is connect-multiparty safe to use?

connect-multiparty has 1 known vulnerabilities on the latest version (2.2.0). DepScope rates its health at 19/100 (critical risk).

What is the latest version of connect-multiparty?

The latest version of connect-multiparty is 2.2.0, released 2018-09-15.

Does connect-multiparty have known vulnerabilities?

Yes. connect-multiparty has 1 known vulnerabilities. See depscope.dev/pkg/npm/connect-multiparty for details.

Is connect-multiparty deprecated?

Yes, connect-multiparty is deprecated: This package is archived and no longer maintained. For support, visit https://github.com/expressjs/express/discussions Consider using ? instead.

What are alternatives to connect-multiparty?

Popular alternatives to connect-multiparty in npm include: ?, minimatch, ansi-styles, brace-expansion, semver.

What license does connect-multiparty use?

connect-multiparty is licensed under MIT.

connect-multiparty

npmv2.2.0deprecated

multipart parsing middleware for connect using multiparty

License MITpermissive20 versions3 maintainers5 deps58,567 weekly dl

expressjs/connect-multiparty

/ 100

Health

find alternative

connect-multiparty is deprecated — find an alternative

Moderate health score (19/100) — verify manually
1 high severity vulnerabilities
Package is deprecated

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

20/25

security

15/15

maturity

4/15

community

Vulnerabilities

1 high

Advisories (1)

Severity	ID	Summary	Fixed in
high	CVE-2022-29623	Connect-Multiparty allows arbitrary file upload	—

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (5)

qs type-is multiparty http-errors on-finished

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/connect-multiparty