pez @4.0.4
Multipart parser
Maintainers
Keywords
Dependencies (5)
| Package | Constraint | Registry Status |
|---|---|---|
| b64 | 4.x.x | auto_approved |
| boom | 7.x.x | auto_approved |
| hoek | 6.x.x | No greenflagged match |
| nigel | 3.x.x | auto_approved |
| content | 4.x.x | No greenflagged match |
Dev Dependencies (5)
| Package | Constraint | Registry Status |
|---|---|---|
| lab | 17.x.x | auto_approved |
| code | 5.x.x | auto_approved |
| wreck | 14.x.x | auto_approved |
| teamwork | 3.x.x | auto_approved |
| form-data | 2.x.x | auto_approved |
Transitive Dependency Tree
Changes from v2.1.5
Dependency Changes
| Change | Package | Version |
|---|---|---|
| changed | b64 | 3.x.x → 4.x.x |
| changed | boom | 5.x.x → 7.x.x |
| changed | hoek | 4.x.x → 6.x.x |
| changed | nigel | 2.x.x → 3.x.x |
| changed | content | 3.x.x → 4.x.x |
File Changes
Risk Dispositions (1 applicable to this version, 0 other)
Accepted rules are downgraded to INFO on future analyses; rejected rules escalate to CRITICAL.
| Rule | Source | Disposition | Author | Reason | |
|---|---|---|---|---|---|
osv:GHSA-g64q-3vg8-8f93 |
osv | reject | AI | AI (osv): Prototype Pollution affects all versions of pez with no fix; package is deprecated in favor of @hapi/pez. Verdict generalizes to every version of this package. |
SAST Findings (3)
[Always reject] All versions of `pez` are vulnerable to Prototype Pollution. A multipart payload can be constructed in a way that one of the parts’ content can be set as the entire payload object’s prototype. If this prototype contains data, it may bypass other validation rules which enforce access and privacy. If this prototype evaluates to null, it can cause unhandled exceptions when the request payload is accessed. ## Recommendation This package is deprecated and is now maintained as `@hapi/pez`. Please update your dependencies to use `@hapi/pez`.
This version was published by a different npm account than previous versions on 2018-11-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
Review Summary
Risk score: 68. Findings: 1 critical (+40), 1 high (+25), 1 low (+3).
Commit: 7cd9718a0815 Browse source
Published to npm: