Ecosystem Standards
Read the submission criteria and code health rules required to be cataloged in the J&K Open Source Initiative.
Repository Submission Criteria
To keep our directory high-quality and safe, all submitted repositories undergo a structural vetting check by admins and community maintainers. Make sure your repository meets the following four standards before submitting:
1. Valid Open Source License
Your project must include a standard open-source license (such as MIT, Apache 2.0, GPL v3, or BSD) located in a root-level LICENSE file. Closed-source or proprietary code is not accepted.
2. Comprehensive README.md
The repository must contain a README.md in the root directory detailing what the project does, installation commands, dependency configuration, and usage examples.
3. No Hardcoded Secrets
Repositories must be free of committed API keys, passwords, database credentials, or secret tokens. Use environment variables (e.g. .env.template) for configuration settings.
4. Originality & Functional Utility
Simple boilerplate projects, default tutorial copies, or forks without new commits are not accepted. The project should have functional code solving a real-world utility or contributing to a framework.
Community Code of Conduct
We strive to build a healthy, welcoming environment for regional technology growth. We expect contributors to respect different viewpoints, offer constructives critiques on reviews, maintain a collaborative attitude, and prioritize clean code and regional mentorship.