Modules does **NOT** host the modules themselves, and only provides downloads to third-party sources. Its database is open source, and is the `apps.json` and `modules.json` files.
Unless a module is labeled `SelfHost`, I am not hosting the file in question.
# Contributing
If you would like to contribute, please know I appreciate it very much!
The backend works on Node.js with Express, EJS, and Tailwind CSS. Each time the code is updated, make sure you run `bun run build:css` to use the latest needed styles.
You can either contribute code (start with `app.js`) or your time to the `apps.json` database and `modules.json`. JSON formatting is pretty easy to learn.
Please create pull requests and issues, and be generally respectful and patient.
-`SelfHost`: If you are hosting the file yourself (or it is on my server), please add the `SelfHost` tag to the module. This will allow users to know that the file is hosted apart from the original source location or one is not avaliable and must be self-hosted. Always use a trusted source (e.g. GitHub) when possible.
-`Root`: If the module requires root access, please add the `Root` tag to the module.
-`FOSS`: If the module is open-source, please add the `FOSS` tag to the module.
## Modules
-`SelfHost`: If you are hosting the file yourself (or it is on my server), please add the `SelfHost` tag to the module. This will allow users to know that the file is hosted apart from the original source location or one is not avaliable and must be self-hosted. Always use a trusted source (e.g. GitHub) when possible.
-`FOSS`: If the module is open-source, please add the `FOSS` tag to the module.
-`Zygisk`: If the module requires Zygisk, please add the `Zygisk` tag to the module.
-`LSPosed`: If the module requires/includes LSPosed (support), please add the `LSPosed` tag to the module.
-`Riru`: If the module requires/includes Riru (support), please add the `Riru` tag to the module.
## Guidelines
1. Always use a trusted source when possible.
2. All pull requests will be manually reviewed to ensure the quality/safety of the database.
3. Please be patient with the review process.
4. If you have any questions, please ask in the Telegram channel (see top of README).