expand-object @0.3.8
Expand a string into a JavaScript object using a simple notation. Use the CLI or as a node.js lib.
Maintainers
Keywords
Dependencies (5)
| Package | Constraint | Registry Status |
|---|---|---|
| minimist | ^1.1.2 | auto_approved |
| get-stdin | ^4.0.1 | auto_approved |
| is-number | ^2.0.2 | auto_approved |
| set-value | ^0.2.0 | No greenflagged match |
| data-store | ^0.8.0 | auto_approved |
Dev Dependencies (1)
| Package | Constraint | Registry Status |
|---|---|---|
| mocha | * | auto_approved |
Transitive Dependency Tree
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-4vjr-hfpp-2m7w |
osv | reject | AI | AI (osv): Prototype Pollution vulnerability covers all versions including 0.4.2 with no fix published; verdict generalizes to all versions in the affected range. |
SAST Findings (2)
[Always reject] CVSS 7.3 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L Versions of the package expand-object from 0.0.0 to 0.4.2 are vulnerable to Prototype Pollution in the expand() function in index.js. This function expands the given string into an object and allows a nested property to be set without checking the provided keys for sensitive properties like __proto__.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
Review Summary
Risk score: 43. Findings: 1 critical (+40), 1 low (+3).
Commit: 819653056a5e Browse source
Published to npm: