Docs: Add Community Health Files (CoC, Contributing, Security) & Update Metadata
@harshentau-spec is already working on this.
Since Jan 3, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by reviewing the root README.md and the repository root on the dev branch, especially the existing contributing guidance and license references. Add CODE_OF_CONDUCT.md, CONTRIBUTING.md, and SECURITY.md, determine and add the appropriate license, and update README.md with Discord and email links; done means all requested community files and metadata are present and consistent.
Written by the indexing model from the issue text.
Description
Is this related to an existing part of the documentation?
- Yes, it is related to an existing section
What needs to be updated?
📌 Current Documentation Issue
The repository currently lacks standard open-source community health files (CODE_OF_CONDUCT.md, CONTRIBUTING.md, SECURITY.md). Additionally, the root README.md is missing critical contact information (Discord/Email links) and refers to a license that hasn't been formally added yet.
✨ Proposed Changes
- Add
CODE_OF_CONDUCT.md: Establish standards for community behavior. - Add
CONTRIBUTING.md: Move contributing guidelines from README to a dedicated file. - Add
SECURITY.md: Define the security policy and reporting process. - Update License: Determine and add the appropriate license.
- Update Contact Info: Add missing Discord and Email links in
README.md.
@Saahi30 I would like to contribute to this project by working on this issue.
Relevant Documentation Link (if any)
https://github.com/AOSSIE-Org/InPactAI/tree/dev
Record
- I agree to follow this project's Code of Conduct
- I want to work on this update
- Dominant language
- TypeScript
- Stars
- 101
- Forks
- 145
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AOSSIE-Org/InPactAI
-
UI Bug: Low contrast makes input text unreadable in Sign Up and Login formPossibly taken @Abhik-Mudi claimed this 308 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AOSSIE-Org/InPactAI#218 ·
-
DOCS UPDATE: Fix incorrect .env file location in Backend Setup instructionsPossibly taken @PulkitDadwal claimed this 322 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 68/100
AOSSIE-Org/InPactAI#201 ·
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
AOSSIE-Org/InPactAI#314 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
AOSSIE-Org/InPactAI#312 ·
-
FEATURE REQUEST: Add API Pagination to Backend List EndpointsMay be free again @alphacoder-hash claimed this 194 days ago, and no pull request is open. Open
Difficulty 4/5 3-5 days Newbie friendliness 50/100
AOSSIE-Org/InPactAI#307 · 2 comments ·
All issues in AOSSIE-Org/InPactAI
Similar issues
-
check:passed streams:add
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
beta technical-medium ui
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
walletbeat/walletbeat#1625 ·
Maintainers usually reply within 1 day
-
[Good First Issue]: Add unit tests for NetworkVersionInfoPossibly taken A pull request linked to this issue is open or already merged. OpenGood First Issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
hiero-ledger/hiero-sdk-js#4489 ·
Maintainers usually reply within 1 day
-
[Bug] The clients language filter cannot select the rows the page labels as unknownPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
apache/rocketmq-dashboard#6103 ·
Maintainers usually reply within 4 days
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
payloadcms/payload#18652 ·
Maintainers usually reply within 1 day