Submit Your Project
Launch your project onto our open registry, connect with collaborators, and audit your code with community reviewers.
Guidelines for Getting Featured on JKOSI
To get your project featured on JKOSI:
- 1
Add an Open-Source License
Include an OSI-approved licence such as Apache 2.0, MIT, GPLv3, AGPLv3, MPL 2.0, or BSD.
- 2
Publish the Complete Source Code
The repository should contain working code, not only screenshots, presentations, or a README. Remove all passwords, keys, personal data, and confidential information.
- 3
Provide Clear Documentation
Your README should explain the problem, solution, technology, setup process, usage, limitations, future plans, and contributor details.
- 4
Give Proper Attribution
Existing ideas may be copied, adapted, or extended, but original projects, authors, datasets, models, APIs, libraries, and templates must be credited.
- 5
Make the Project Reproducible
Include dependency files, environment examples, database instructions, dataset or model links, and clear steps to run or deploy the project.
- 6
Be Transparent
Clearly mention what works, what is incomplete, which features are simulated, and whether AI-generated code or starter templates were used.
- 7
Respect Privacy and Intellectual Property
Do not publish private data, copyrighted material, proprietary code, or confidential information without permission.
- 8
Support Community Contributions
Enable issues, pull requests, bug reports, contribution guidelines, and clear maintainer contact details.
Please Note: Being listed on JKOSI does not mean that JKOSI endorses every claim made by a project. It means that the project has been documented as part of the growing open-source ecosystem.
JKOSI reserves the right to request clarification, suggest improvements, change the listing category, temporarily withhold a project, or remove a listing in cases involving plagiarism, false claims, licence violations, privacy risks, harmful content, or misuse of intellectual property.
Our objective is not only to list projects, but to build a trusted community asset that documents problems, solutions, experiments, implementations, and learnings.