Skip to content

Commit 90e2e61

Browse files
Add security policy (SECURITY.md)
Co-authored-by: Cursor <cursoragent@cursor.com>
1 parent fcf9ad2 commit 90e2e61

1 file changed

Lines changed: 92 additions & 0 deletions

File tree

SECURITY.md

Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
| Version | Supported |
6+
| ------- | ------------------ |
7+
| 1.0.x | :white_check_mark: |
8+
9+
## Reporting a Vulnerability
10+
11+
We take the security of Crypto Miner Optimizer seriously. If you discover a security vulnerability, please follow these steps:
12+
13+
### How to Report
14+
15+
1. **Do NOT** create a public GitHub issue for security vulnerabilities
16+
2. Email your findings to the repository maintainer directly
17+
3. Include as much detail as possible:
18+
- Type of vulnerability
19+
- Steps to reproduce
20+
- Potential impact
21+
- Suggested fix (if any)
22+
23+
### What to Expect
24+
25+
- **Acknowledgment**: We will acknowledge receipt of your report within 48 hours
26+
- **Updates**: We will provide updates on the status of your report within 7 days
27+
- **Resolution**: We aim to resolve critical vulnerabilities within 30 days
28+
29+
### Scope
30+
31+
The following are considered in-scope for security reports:
32+
33+
- Authentication/authorization bypasses
34+
- Cross-site scripting (XSS)
35+
- Code injection vulnerabilities
36+
- Sensitive data exposure
37+
- Insecure data storage
38+
- Dependency vulnerabilities with exploitable impact
39+
40+
### Out of Scope
41+
42+
- Vulnerabilities in third-party dependencies without demonstrated impact
43+
- Social engineering attacks
44+
- Physical security issues
45+
- Denial of service attacks
46+
47+
## Security Best Practices for Users
48+
49+
### Running the Application
50+
51+
1. **Offline Mode**: The application is designed to run fully offline. No sensitive data is transmitted externally
52+
2. **Local Storage**: All data is stored locally on your machine
53+
3. **No API Keys**: The application does not require or store API keys for external services
54+
55+
### Data Protection
56+
57+
- GPU settings and mining profiles are stored locally
58+
- No wallet addresses or private keys are stored by the application
59+
- Profitability calculations use publicly available market data
60+
61+
### Network Security
62+
63+
- The Qt desktop application blocks all external network requests by default
64+
- Web version can be run entirely offline after initial load
65+
- No telemetry or analytics data is collected
66+
67+
## Security Features
68+
69+
- **Encrypted Badge**: Application operates with local data encryption
70+
- **Offline Operation**: Full functionality without internet connection
71+
- **Request Blocking**: Qt wrapper blocks all external network requests
72+
- **No External Dependencies**: Core functionality works without external API calls
73+
74+
## Dependency Security
75+
76+
We actively monitor and update dependencies to address known vulnerabilities:
77+
78+
```bash
79+
# Check for vulnerabilities
80+
npm audit
81+
82+
# Fix non-breaking vulnerabilities
83+
npm audit fix
84+
```
85+
86+
## Acknowledgments
87+
88+
We appreciate security researchers who help keep Crypto Miner Optimizer secure. Contributors who report valid security issues will be acknowledged here (with permission).
89+
90+
---
91+
92+
*Last updated: February 2026*

0 commit comments

Comments
 (0)