@@ -62,68 +62,3 @@ We appreciate responsible disclosure and will:
6262## 🙏 Acknowledgements
6363
6464Thanks to all contributors who help keep CommitPulse secure.
65-
66- # 🔐 Security Policy
67-
68- ## 📢 Reporting a Vulnerability
69-
70- We take the security of CommitPulse seriously. If you discover a vulnerability, please report it responsibly.
71-
72- - Please contact maintainers via GitHub (preferred)
73-
74- Please include:
75-
76- - Description of the vulnerability
77- - Steps to reproduce
78- - Potential impact
79- - Suggested fix (if possible)
80-
81- ⚠️ Please do NOT create public issues for security vulnerabilities.
82-
83- ---
84-
85- ## 🛡️ Supported Versions
86-
87- We aim to support the latest version of CommitPulse.
88-
89- | Version | Supported |
90- | ------- | --------- |
91- | Latest | ✅ Yes |
92- | Older | ❌ No |
93-
94- ---
95-
96- ## 🔒 Security Best Practices
97-
98- To keep your usage secure:
99-
100- - Always install from trusted sources
101- - Avoid running the tool on untrusted repositories
102- - Keep your dependencies updated
103- - Do not expose sensitive tokens or credentials
104-
105- ---
106-
107- ## 🔐 Data & Privacy
108-
109- CommitPulse is designed with privacy in mind:
110-
111- - No source code is uploaded or stored
112- - Only Git metadata is analyzed
113- - Local analysis mode ensures full control over your data
114-
115- ---
116-
117- ## ⚙️ Responsible Disclosure
118-
119- We appreciate responsible disclosure and will:
120-
121- - Respond within 48–72 hours
122- - Investigate and fix issues promptly
123- - Credit contributors (if desired)
124-
125- ---
126-
127- ## 🙏 Acknowledgements
128-
129- Thanks to all contributors who help keep CommitPulse secure.
0 commit comments