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

[BUG]: Contributor Intelligence returns HTTP 422 when fetching contributor details

Open
#232 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github, javascript
Domain
analytics, api

Research direction

Start on the Contributor Intelligence page and reproduce the request for priyanshunitr in AOSSIE-Org using the default reporting window. Inspect the failing GitHub API request in DevTools → Network and compare its parameters and authentication with the manually successful request; done means contributor details load without HTTP 422.

Written by the indexing model from the issue text.

Description

bug
Bug Description

The Contributor Intelligence page fails to fetch contributor details and displays:

Failed to fetch contributor details: HTTP 422

The GitHub API request works correctly when executed manually with the same query and authentication token, but the request made from the web application returns 422 Unprocessable Content.

Steps to Reproduce
  1. Open the Contributor Intelligence page.
  2. Search for the GitHub username priyanshunitr.
  3. Select the organization AOSSIE-Org.
  4. Use the default reporting window.
  5. Open DevTools → Network.
  6. Observe the GitHub API requests.
Logs and Screenshots
Image
Environment Details
Environment
  • OS: Windows 10/11
  • Browser: Brave 153.0.0.0
  • Device: Desktop
  • GitHub API: REST API (api.github.com)
  • Application: AOSSIE Org Explorer
Impact

High - Major feature is broken

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
2d 17h
Merged PRs (30d)
10

Contributor guide

Open the contributing guide

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.