Lodash modular utilities.
89%
Total Score
100
94
90
50
No registry build attestation or trusted-publisher provenance is present, leaving the publication path less transparent than an attested release. Repository build and security tooling provide partial compensation but do not remove this gap.
Six of eight workflows lack top-level permission declarations, which weakens explicit least-privilege documentation even though none declares top-level write access and two specify read-only permissions.
No type declarations are bundled, which can reduce integration ergonomics for TypeScript consumers, though it does not indicate abandonment or unfitness for JavaScript use.
| Title | Versions | Severity |
|---|---|---|
CVE-2026-4800 lodash is vulnerable to Improper Control of Generation of Code ('Code Injection') in versions 4.0.0 - 4.17.23. | 4.0.0 - 4.17.23 | High |
CVE-2026-2950 lodash is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in versions 0.0.0 - 4.17.23. | 0.0.0 - 4.17.23 | Medium |
CVE-2025-13465 lodash is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in versions 4.0.0 - 4.17.22. | 4.0.0 - 4.17.22 | Medium |
CVE-2020-28500 lodash is vulnerable to Uncontrolled Resource Consumption in versions 4.0.0 - 4.17.21. | 4.0.0 - 4.17.21 | Medium |
CVE-2021-23337 lodash is vulnerable to Improper Neutralization of Special Elements used in a Command ('Command Injection') in versions 0.0.0 - 4.17.21. | 0.0.0 - 4.17.21 | High |
No direct dependencies.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.