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

[FEATURE]: Expand Community Files audit checklist on the Governance dashboard

Open
  • Is something wrong?
#182 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@AbiramiR-27 is already working on this.

Since Aug 21, 2026.

  • #185 by @AbiramiR-27 — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github, javascript
Domain
api, frontend

Research direction

Start by reading the existing repository audit logic in src/services/github.js and the Governance dashboard in src/pages/GovernancePage.jsx. Check how current licensing and metrics are fetched and displayed, then use the listed GitHub community-profile or standard paths as the reference for the four checks. Done means each repository shows a status for CODE_OF_CONDUCT.md, CONTRIBUTING.md, issue templates, and pull request templates.

Written by the indexing model from the issue text.

Description

enhancement
Feature and its Use Cases
Feature Description

Currently, the Governance dashboard checks for basic repository licensing and some primary metrics. However, it does not audit other essential community health files required by standard open-source organizations.

This feature request proposes extending the repository audit checklist to verify and display the presence of the following files/configurations:

  1. CODE_OF_CONDUCT.md (Code of Conduct)
  2. CONTRIBUTING.md (Contributing Guidelines)
  3. Issue Templates (checking the .github/ISSUE_TEMPLATE/ directory)
  4. Pull Request Template (.github/pull_request_template.md or .github/PULL_REQUEST_TEMPLATE.md)
Use Cases
  • Open Source Compliance Auditing: Helps maintainers and organization administrators quickly verify if all repositories in their portfolio conform to standard community health file requirements.
  • Contributor Onboarding Audit: Helps developers identify which repositories need templates or contribution guidelines created, making it easier for new contributors to submit structured issues and PRs.
Additional Context
Suggested Implementation
  • In src/services/github.js, add helper methods to fetch the community profile or check contents at standard paths (e.g. https://api.github.com/repos/{owner}/{repo}/community/profile).
  • In the Governance dashboard UI (src/pages/GovernancePage.jsx), render a detailed checklist status grid under each repository row (e.g. using small green/red indicators or ticks/crosses for each file).
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.