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

[BUG]: Dead Issues and Zombie PRs tabs only show first 25 items with no pagination

Open Beginner friendly
#260 2 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
84/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

Start in src/pages/GovernancePage.jsx and inspect the Dead Issues and Zombie PRs tab rendering around the .slice(0, 25) calls. Reproduce with an organization containing more than 25 results, then verify that users can access every result and that the displayed count remains consistent with the visible data.

Written by the indexing model from the issue text.

Description

bug
Bug Description

The "Dead Issues" and "Zombie PRs" tabs on the Governance page hard-cap results to the first 25 items using .slice(0, 25), with no pagination or way to view items beyond that limit. Organizations with more than 25 dead issues or zombie PRs will have the remaining data permanently hidden from the user.

Steps to Reproduce
  1. Go to the Governance page for an organization with 25+ dead issues
    or zombie PRs
  2. Click the Run Audit Button
  3. Open the "Dead Issues" or "Zombie PRs" tab
  4. Notice only 25 rows are shown, with no page controls or way to see more, even though the tab count badge may show a higher number
Logs and Screenshots

No response

Environment Details
  • OS: Windows 11 / macOS / Linux
  • Browser: Chrome 120 / Firefox / Safari
  • Relevant file: src/pages/GovernancePage.jsx
Impact

Critical - Application is unusable

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
Dominant language
JavaScript
Stars
35
Forks
98
Avg merge
1d 21h
Merged PRs (30d)
9

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 AOSSIE-Org/OrgExplorer

All issues in AOSSIE-Org/OrgExplorer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.