Skip to content

[Snyk] Security upgrade less-cache from 1.1.0 to 1.1.1 - #136

Closed
jhamot wants to merge 1 commit into
masterfrom
snyk-fix-d3a872d3ab230a20674d68317d2127f1
Closed

[Snyk] Security upgrade less-cache from 1.1.0 to 1.1.1#136
jhamot wants to merge 1 commit into
masterfrom
snyk-fix-d3a872d3ab230a20674d68317d2127f1

Conversation

@jhamot

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

IssueScore
medium severityAllocation of Resources Without Limits or Throttling
SNYK-JS-QS-15268416
62

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note:You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

@jhamot

Copy link
Copy Markdown
OwnerAuthor

Merge Risk: Low

This is a patch version upgrade for less-cache. There is no readily available changelog for this specific version, but as a patch release, it is expected to contain only minor bug fixes and no breaking changes.

Source: Package documentation

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@jhamotjhamot closed this Jun 15, 2026
@jhamot

Copy link
Copy Markdown
OwnerAuthor

✅ This PR has been automatically closed

The security issues addressed by this pull request are no longer present in the latest project scan. All vulnerabilities this PR was created to fix have been resolved through other means (e.g., dependency updates, direct fixes, or changes in vulnerability data).

Resolved Issues

  • SNYK-JS-QS-15268416

What should I do?

No action is required. If you believe this PR was closed in error, you can reopen it and contact Snyk support.


This action was performed automatically by Snyk.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@jhamot@snyk-bot