Skip to content

Potential lodash vulnerability at 4.17.11 #21

@quetzaluz

Description

@quetzaluz

Note: This feels somewhat lower priority because the vulnerable methods in question aren't used, but resolving this can can fix package installation/audit warnings and prevent accidental usage of vulnerable methods:

Similar to #13, lodash requires another upgrade due to a reported vulnerability in the version used in this repo:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions