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
Copy file name to clipboardExpand all lines: SECURITY.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,7 @@ Avoid sending live secrets (such as real private keys or production credentials)
73
73
74
74
We ask all reporters to follow responsible disclosure principles:
75
75
76
-
* Report vulnerabilities **privately and confidentially** through the appropriate channel (CE → Lab Leader / LFDT; EE → Alveoli CTO).
76
+
* Report vulnerabilities **privately and confidentially** through the appropriate channel (CE → Lab Leader / LFDT; EE → Alveoli CEO).
77
77
* Allow the relevant team (GitMesh CE maintainers or Alveoli for EE) a reasonable period to investigate, fix, and coordinate disclosures.
78
78
* Do not intentionally exploit the vulnerability beyond what is necessary to confirm its existence.
79
79
* Do not access, modify, or destroy data that does not belong to you.
@@ -107,7 +107,7 @@ If escalation is needed (for example, for broader LFDT concerns), CE issues may
107
107
108
108
### For EE Reports
109
109
110
-
When you report a potential vulnerability in GitMesh EE to the CTO of Alveoli, it will be handled through Alveoli’s internal security and product processes. This includes triage, validation, remediation, and any appropriate communication to GitMesh EE operators or customers, managed exclusively by Alveoli.
110
+
When you report a potential vulnerability in GitMesh EE to the CEO of Alveoli, it will be handled through Alveoli’s internal security and product processes. This includes triage, validation, remediation, and any appropriate communication to GitMesh EE operators or customers, managed exclusively by Alveoli.
111
111
112
112
While specific timelines cannot be guaranteed, all reports are taken seriously and handled in good faith.
113
113
@@ -214,7 +214,7 @@ Users should keep GitMesh, underlying operating systems, and related infrastruct
214
214
***GitMesh CE Security – Lab Leader (Ryan Madhuwala)**
215
215
`rawx18.dev@gmail.com`
216
216
217
-
***GitMesh EE Security – CTO of Alveoli (Ryan Madhuwala)**
217
+
***GitMesh EE Security – CEO of Alveoli (Ryan Madhuwala)**
Copy file name to clipboardExpand all lines: governance/premium.LICENSE
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# **GitMesh Enterprise Edition (EE) License**
2
2
3
-
Copyright (c) 2026-present Alveoli
3
+
Copyright (c) 2026-present Alveoli (alveoli.app)
4
4
5
5
The GitMesh Enterprise Edition software and all associated documentation (the “Software”) is proprietary to Alveoli and is not intended for public use. The Software may be used in a production environment only if you, and any entity you represent, have agreed to and remain in compliance with the GitMesh Subscription Terms of Service or another written agreement governing your use of the Software, and only while maintaining an active GitMesh Enterprise Edition subscription for the correct number of user seats or the applicable tier, including Essential, Signals, Scale, or Enterprise. Any production use of the Software without an active subscription is strictly prohibited.
0 commit comments