Skip to content

Commit 946d322

Browse files
docs: add security policy and vulnerability reporting guidelines (#4069)
Adding a SECURITY.md helps us make two things clearer: - MagicMirror is not intended for direct public internet exposure. - There is a clear path to report security concerns responsibly. Related issue: #4067 --- As always, suggestions for improvement are very welcome.
1 parent 51f6927 commit 946d322

1 file changed

Lines changed: 31 additions & 0 deletions

File tree

.github/SECURITY.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# Security Policy
2+
3+
## Scope and Deployment
4+
5+
MagicMirror is primarily intended for trusted local/private network environments.
6+
Direct public exposure to the internet or other untrusted networks is not recommended.
7+
8+
We take security seriously and encourage responsible disclosure of vulnerabilities to help us improve the software.
9+
10+
## Reporting a Vulnerability
11+
12+
**Please keep vulnerability details private** — do not post them in public GitHub issues.
13+
14+
Instead, reach out privately via the MagicMirror forum to one of the core developers:
15+
16+
- [rejas](https://forum.magicmirror.builders/user/rejas)
17+
- [karsten13](https://forum.magicmirror.builders/user/karsten13)
18+
- [sdetweil](https://forum.magicmirror.builders/user/sdetweil)
19+
- [Kristjan](https://forum.magicmirror.builders/user/kristjanesperanto)
20+
21+
Please include, if possible:
22+
23+
- Affected version(s)
24+
- Reproduction steps or proof-of-concept
25+
- What could an attacker do with this?
26+
- Any ideas how to fix it?
27+
28+
## Coordinated Disclosure
29+
30+
We will keep reported vulnerabilities private until a fix is available and coordinate the disclosure timeline with you.
31+
We aim to respond as quickly as possible.

0 commit comments

Comments
 (0)