SECURITY.md

README.md

@@ -4,7 +4,7 @@ Generally, memo features are opt-in.
 Clients can choose whether to support or not support each action.
 For instance, Wewo has [blogs](https://wewo.cash/blogs/) and
 Memberapp has [maps](https://memberapp.github.io/#map).
-Memo.cash doesn't yet support either feature.
+Memo.cash does yet support either feature.
 
 Since consensus is not required, there isn't currently a need for a strict approval process.
 However, sharing protocol additions and motivations is helpful for healthy collaboration.
@@ -20,3 +20,4 @@ However, sharing protocol additions and motivations is helpful for healthy colla
 | MIP-6 | [Commerce](mip-0006/mip-0006.md) | 2018-11-17 | Draft |
 | MIP-7 | [Gigs](mip-0007/mip-0007.md) | 2018-12-07 | Draft |
 | MIP-9 | [Token exchange](mip-0009/mip-0009.md) | 2019-06-05 | Final (v2) |
+

SECURITY.md

@@ -0,0 +1,23 @@
+# Security Policy
+@uvhw
+
+## Supported Versions
+
+Use this section to tell people about which versions of your project are
+currently being supported with security updates.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 5.1.x   | :white_check_mark: |
+| 5.0.x   | :x:                |
+| 4.0.x   | :white_check_mark: |
+| < 4.0   | :x:                |
+
+## Reporting a Vulnerability
+
+Use this section to tell people how to report a vulnerability.
+
+Tell them where to go, how often they can expect to get an update on a
+reported vulnerability, what to expect if the vulnerability is accepted or
+declined, etc.
+