Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

site: [email protected] has 3 critical advisories; bump Next to >=16.3.6

Open Beginner friendly
#1,091 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bun, next.js
Domain
build-system

Research direction

Start in site/package.json: bump next and eslint-config-next to >=16.3.6, then check whether the sharp override added in #1090 is still required once Next's own range admits >=0.35.5. Reinstall from site/ with a frozen lockfile, then confirm with bun run build and bun audit that GHSA-p293-qw3h-jr36, GHSA-2xp9-vwfh-vxw4 and GHSA-vcvr-r3jv-pc5j no longer appear. Done means the three critical advisories are gone with receipts; the Bun-on-PATH pinning note is secondary scope.

Written by the indexing model from the issue text.

Description

From the #1090 Opus review (bun audit on site/, after the sharp fix). There are 3 pre-existing CRITICAL advisories, all in [email protected], fixed in Next >=16.3.6: GHSA-p293-qw3h-jr36, GHSA-2xp9-vwfh-vxw4, GHSA-vcvr-r3jv-pc5j. Plus 34 high, 17 moderate and 3 low remaining (57 total).

Expected: an XS/S PR bumping next (and eslint-config-next) to >=16.3.6. Check whether the sharp override from #1090 is still needed afterwards (Next's own range may then allow >=0.35.5), and keep frozen install, bun run build and bun audit receipts. Also noted: two Bun binaries are on PATH (~/.bun/bin 1.3.9 shadows Homebrew 1.4.2); pin which one CI and the hooks use.

Reported by the BrainLayer lead (post-convergence backlog).

Dominant language
Python
Stars
9
Forks
7
Avg merge
4h 50m
Merged PRs (30d)
404

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EtanHey/brainlayer

All issues in EtanHey/brainlayer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.