🚨 [security] [js] Update serve-static 1.14.1 → 1.16.0 (minor) - #169
Open
depfu[bot] wants to merge 1 commit into
Open
🚨 [security] [js] Update serve-static 1.14.1 → 1.16.0 (minor)#169depfu[bot] wants to merge 1 commit into
depfu[bot] wants to merge 1 commit into
Conversation
Vulnerable Libraries (2)
More info on how to fix Vulnerable Libraries in JavaScript. 👉 Go to the dashboard for detailed results. 📥 Happy? Share your feedback with us. |
depfu
Bot
force-pushed
the
depfu/update/yarn/serve-static-1.16.0
branch
from
August 7, 2026 01:06
6cff2a4 to
a7a8da5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ serve-static (1.14.1 → 1.16.0) · Repo · Changelog
Security Advisories 🚨
🚨 serve-static vulnerable to template injection that can lead to XSS
Release Notes
1.15.0
1.14.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 44 commits:
1.16.0Merge commit from fork1.15.0docs: update CI linkbuild: Node.js@17.8deps: send@0.18.0build: mocha@9.2.2build: Node.js@17.7build: supertest@6.2.2build: mocha@9.2.1build: Node.js@17.5build: Node.js@16.14build: Node.js@14.19build: mocha@9.2.0build: supertest@6.2.1build: Node.js@17.3build: eslint-plugin-import@2.25.4build: remove package-lock1.14.2tests: add tests for non-existent root pathdocs: fix a typo in the readmedeps: send@0.17.2build: eslint-plugin-promise@5.2.0build: use nyc for coverage testingbuild: support Node.js 17.xbuild: mocha@9.1.3build: safe-buffer@5.2.1build: mocha@8.4.0build: supertest@6.1.6build: eslint-plugin-standard@4.1.0lint: apply standard 14 stylebuild: eslint-plugin-markdown@2.2.1build: mocha@7.2.0build: support Node.js 16.xbuild: support Node.js 15.xbuild: support Node.js 14.xbuild: support Node.js 13.xbuild: Node.js@12.22build: mocha@6.2.3lint: apply standard 13 stylebuild: eslint-plugin-import@2.25.2build: Node.js@12.19build: Node.js@10.24build: use GitHub Actions instead of Travis CIDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.