Skip to content

sharp v < 0.35.0 security vulnerability breaking changes if updated? #2543

Description

@eclecticpassions

I am on the latest Quartz v5 (just ran npm quartz upgrade) and saw the node_module sharp is vulnerable with "high serverity". Can the upstream Quartz dependencies be updates so that users can npm audit fix without --force? Thanks a lot.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions