Track the deepmerge advisory that has no patched release
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, typescript
- Domain
- devops
Research direction
Start by reading the dependency declarations and lockfile entries for deepmerge, @svgr/plugin-svgo, and the Docusaurus packages, then check whether a release newer than 4.3.1 is available. When one is available, update the dependency and run npm audit; done means the advisory is gone without downgrading Docusaurus. Until then, the issue says to leave the dependency unchanged.
Written by the indexing model from the issue text.
Description
Summary
After the November pin pass (#392), npm audit has no high or moderate findings. The remaining low is one advisory, repeated through the SVGR chain:
deepmerge>= 4.2.0(GHSA-gcqx-w48m-w2h4)- Pulled in by
@svgr/plugin-svgo, then@svgr/webpack,@docusaurus/plugin-svgr, and@docusaurus/preset-classic - Newest 4.x release is 4.3.1, which is still inside the range
@svgr/plugin-svgorequires^4.3.1, so an override to an older 4.x is outside the version that package asks for
npm audit fix --force wants to downgrade @docusaurus/preset-classic to 3.6.3. Do not do that.
This is separate from #339, which is the braces advisory. #338 should keep failing only on high and critical, so this low must not turn the build red. It still needs a place to be revisited.
What to change
- Leave the dependency where it is.
- When a
deepmergerelease newer than 4.3.1 is published, bump it and confirmnpm auditno longer reportsGHSA-gcqx-w48m-w2h4. - Until then, do not allow-list it by downgrading Docusaurus.
Acceptance
- The issue stays open until a patched
deepmergeexists - No pull request downgrades Docusaurus to clear this one low
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 24
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 34
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from IntersectMBO/developer-experience
-
documentation enhancement Low Priority
Difficulty 1/5 Under an hour Newbie friendliness 72/100
IntersectMBO/developer-experience#397 ·
Maintainers usually reply within 2 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
IntersectMBO/developer-experience#376 ·
Maintainers usually reply within 2 days
-
documentation pinned
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
IntersectMBO/developer-experience#363 ·
Maintainers usually reply within 2 days
-
documentation pinned
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
IntersectMBO/developer-experience#362 ·
Maintainers usually reply within 2 days
-
documentation pinned
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
IntersectMBO/developer-experience#360 ·
Maintainers usually reply within 2 days
All issues in IntersectMBO/developer-experience
Similar issues
-
bug parity
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
WenyuChiou/agent-board#1489 ·
Maintainers usually reply within 1 day
-
area: bazaar bug complexity: medium
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
accensa/x402-facilitator-stellar#779 ·
Maintainers usually reply within 1 day
-
bug good first issue P4 size:S web-ui
Difficulty 2/5 Half a day Newbie friendliness 85/100
josephfung/curia#2600 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cloudflare/partykit#444 ·