You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -154,16 +170,6 @@ GitHub® is a registered trademark of GitHub, Inc.
154
170
- Android: opens APK downloads with the package installer, tracks installations in a local database, and shows them in a dedicated Apps screen with update indicators.
155
171
- Desktop (Windows/macOS/Linux): downloads installers to the user’s Downloads folder and opens them with the default handler; no hidden temp locations.
156
172
157
-
-**Appearance & theming**
158
-
- Material 3 design with **Material 3 Expressive** components on all platforms.
159
-
- Material You dynamic color support on Android where available.
160
-
- Optional AMOLED black mode for dark theme on OLED devices.
161
-
162
-
-**Safety & inspection (Android)**
163
-
- Optional GitHub sign‑in via OAuth device flow for higher rate limits with minimal scopes.
164
-
- “Open in AppManager” action to inspect an APK’s permissions and trackers before installing.
-**Client Secret** ← ❗ NOT required for this project
293
+
294
+
### 3 - Add It to Your Project
295
+
Open your project’s `local.properties` file (root of the project) and add:
296
+
```properties
297
+
GITHUB_CLIENT_ID=YOUR_CLIENT_ID_HERE
298
+
```
299
+
300
+
### 4 - Sync & Run
301
+
Sync the project and run the app. You should now be able to sign in with GitHub.
302
+
303
+
### ❗ Important Notes
304
+
-`local.properties` is **not committed to Git**, so your Client ID stays local.
305
+
- This project only needs the **Client ID** (not the Client Secret).
306
+
- Each developer should create their own OAuth app for development.
307
+
308
+
</details>
309
+
310
+
---
311
+
295
312
## ☕ Support the project
296
313
297
314
**GitHub Store** has reached **48,000+ active users** and **5,500+ GitHub stars** — and it's **100% free** with no ads, no tracking, and no premium features.
@@ -316,30 +333,9 @@ I built and maintain this entirely on my own while finishing high school. Your s
316
333
- ⭐ **Starring this repo** — helps others discover GitHub Store
317
334
- 🐛 **Reporting bugs** — makes the app better for everyone
318
335
- 📢 **Sharing with friends** — spread the word to other developers
319
-
- 💬 **Joining discussions** — your feedback shapes the roadmap
336
+
- 💬 **Joining our [Discord](https://discord.gg/x9Cvh2Z9qS)** — your feedback shapes the roadmap
320
337
321
-
Every bit of support—financial or not—means the world and keeps this project alive. Thank you! 🙏
We take the security of this repository seriously. If you discover a security vulnerability, please report it responsibly.
6
+
7
+
**Please do not open a public GitHub issue for security vulnerabilities.**
8
+
9
+
Instead, use one of the following methods:
10
+
11
+
-**GitHub Security Advisories**
12
+
Use the "Report a vulnerability" feature available in the repository’s **Security** tab.
13
+
14
+
-**Email**
15
+
Send a detailed report to: [rainxch.dev@gmail.com](mailto:rainxch.dev@gmail.com)
16
+
17
+
---
18
+
19
+
## What to Include in Your Report
20
+
21
+
To help us assess and resolve the issue quickly, please include:
22
+
23
+
- A clear description of the vulnerability
24
+
- Steps to reproduce the issue
25
+
- Proof of concept (PoC), if available
26
+
- Affected files, endpoints, or components
27
+
- Potential impact of the vulnerability
28
+
29
+
---
30
+
31
+
## Response Timeline
32
+
33
+
We aim to follow this general timeline:
34
+
35
+
-**Acknowledgement:** Within 48 hours
36
+
-**Initial assessment:** Within 5 business days
37
+
-**Fix or mitigation:** Based on severity and complexity
38
+
39
+
Timelines may vary depending on the nature of the vulnerability.
40
+
41
+
---
42
+
43
+
## Coordinated Disclosure
44
+
45
+
We kindly request that you practice responsible disclosure and avoid sharing details publicly until the vulnerability has been addressed or a fix has been released.
46
+
47
+
---
48
+
49
+
## Security Best Practices
50
+
51
+
Contributors are encouraged to:
52
+
53
+
- Follow secure coding practices
54
+
- Avoid committing secrets or credentials
55
+
- Use dependency scanning and security tools where possible
56
+
- Review pull requests for potential security issues
57
+
58
+
---
59
+
60
+
## Thank You
61
+
62
+
We appreciate the efforts of the security community and responsible researchers who help keep this project secure.
0 commit comments