Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
57 lines (40 loc) · 2.8 KB

CONTRIBUTING.md

File metadata and controls

57 lines (40 loc) · 2.8 KB
Raw

Contributing to isroot.in

Thank you for your interest in contributing to isroot.in! We welcome contributions from the community to help students and developers launch their ideas.

🚨 Acceptable Use Policy (Read Before Using)

isroot.in is a developer community, not a file host. By using our registry or contributing to this repository, you agree to the following strictly enforced rules.

🚫 Strictly Prohibited Content

We verify all domains via Certificate Transparency logs. If you deploy any of the following, your subdomain will be immediately deleted and your account banned:

  1. Piracy / IPTV Panels: (e.g., Xtream UI, Stalker Middleware, illegal streaming dashboards).
  2. Phishing / Deceptive Sites: Any site mimicking banks, login pages, or crypto services.
  3. Malware / C2: Command and control infrastructure or malware distribution.
  4. Bulk / SEO Spam: Creating 5+ subdomains for the purpose of link farming or SEO manipulation.
  5. Adult Content: Hosting pornography or sexually explicit material.

🛡️ Enforcement

  • Zero Tolerance: We do not provide warnings for phishing or piracy.
  • Reporting: We report repeat offenders to Google Safe Browsing and their ISP.

🛠️ How to Contribute Code

If you want to improve the isroot.in infrastructure or dashboard:

  1. Fork the repository.
  2. Create a branch: git checkout -b feature/AmazingFeature
  3. Commit your changes: git commit -m 'Add some AmazingFeature'
  4. Push to the branch: git push origin feature/AmazingFeature
  5. Open a Pull Request.

Reporting Bugs

If you find a bug in the dashboard, please open an Issue using the "Bug Report" template.

DO NOT open public issues for security vulnerabilities. See SECURITY.md.

Frontend contributions

Submit changes to pages, components, styles, public assets, or browser helpers. Keep existing file paths and /api/* contracts so reviewed changes can be brought into the private application. Coordinate API contract changes with a maintainer. Do not submit backend handlers, database models, secrets, or application data.

Before submitting, run npm ci, npm run typecheck, and npm run build. For Markdown documentation changes, also run npm run docs:build. Describe affected screens and include screenshots for visual changes where useful. Without the private backend, authenticated flows cannot be verified locally; maintainers validate those flows in the complete app before deployment.

Maintainers review public pull requests and import only approved frontend changes into a private branch, preserving private backend code and deployment configuration. Frontend package changes must be reconciled with the private dependency manifest rather than replacing that manifest with this repository's frontend-only version.