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

[FEATURE]: Add Language column in Repository Explorer table

Open Beginner friendly
  • Is something wrong?
#309 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@ProgrammerNesi is already working on this.

Since Oct 5, 2026.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

Start in src/pages/RepositoriesPage.jsx and read how the Repository Explorer table defines its columns and renders repository data; compare this with the existing Language filter. The issue says each repository's language value is already available in the fetched data. Done when the table displays that language for each repository without additional API requests.

Written by the indexing model from the issue text.

Description

enhancement
Feature and its Use Cases

Add a Language column to the Repository Explorer table in src/pages/RepositoriesPage.jsx.

Currently, the repository table displays Repository, Stars, Forks, Open Issues, Health, and Repository Activity, but does not show the languages used by each repository.

How would users benefit from it?
  • Instant technology-stack visibility while scanning repositories.
  • Faster repository comparison without opening individual repository pages.
  • No additional API cost if the language data already exists in the fetched repository data used by the filter/export functionality.
  • Consistent UX with the existing Language filter and language distribution/technology-stack views.
What scenarios would this feature address?
  • Exploring large organizations: Quickly distinguish Python, JavaScript, Go, TypeScript, etc. repositories at a glance.
  • Filtering repositories: After selecting a language filter, users can immediately verify the language of each displayed repository.
  • Repository triage: Identify repositories matching a developer's familiar technology stack without opening each repository.
  • Onboarding and exploration: Quickly understand the technologies used across an organization's repositories.
Additional Context

GitHub’s GET /orgs/{org}/repos API already returns a language field for each repository, and OrgExplorer preserves this data through { ...repo } into model.totalRepos. Therefore, r.language is already available in the existing repository data, making this feature easier to implement with zero additional API requests.

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
42
Forks
124
Avg merge
2d 22h
Merged PRs (30d)
10

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.