fix: update stale org and email references in SECURITY.md and SUPPORT.md

Replace remaining Hawksight-AI GitHub org links and the old
semantica-dev noreply email with the current semantica-agi org
and kaif@getsemantica.ai contact, so security/support contacts
match pyproject.toml.
This commit is contained in:
KaifAhmad1
2026-07-18 18:44:10 +05:30
parent 4e973fcc30
commit 084fb44f05
2 changed files with 11 additions and 11 deletions
+3 -3
View File
@@ -24,7 +24,7 @@ Security vulnerabilities should be reported privately to prevent potential explo
### 2. Report Security Issue
Create a [GitHub Security Advisory](https://github.com/Hawksight-AI/semantica/security/advisories/new) or contact us through [GitHub Issues](https://github.com/Hawksight-AI/semantica/issues) with "[SECURITY]" prefix.
Create a [GitHub Security Advisory](https://github.com/semantica-agi/semantica/security/advisories/new) or contact us through [GitHub Issues](https://github.com/semantica-agi/semantica/issues) with "[SECURITY]" prefix.
Include the following information:
@@ -156,8 +156,8 @@ We appreciate responsible disclosure. Security researchers who help us improve t
For security-related questions or concerns:
- **GitHub Issues**: [Create an issue](https://github.com/Hawksight-AI/semantica/issues) with "[SECURITY]" prefix
- **GitHub Security Advisories**: [Report vulnerability](https://github.com/Hawksight-AI/semantica/security/advisories/new)
- **GitHub Issues**: [Create an issue](https://github.com/semantica-agi/semantica/issues) with "[SECURITY]" prefix
- **GitHub Security Advisories**: [Report vulnerability](https://github.com/semantica-agi/semantica/security/advisories/new)
## Additional Resources
+8 -8
View File
@@ -20,8 +20,8 @@ Start with our comprehensive documentation:
**Best for**: General questions, feature discussions, and getting help
- [Ask a question](https://github.com/Hawksight-AI/semantica/discussions/new?category=q-a)
- [Browse discussions](https://github.com/Hawksight-AI/semantica/discussions)
- [Ask a question](https://github.com/semantica-agi/semantica/discussions/new?category=q-a)
- [Browse discussions](https://github.com/semantica-agi/semantica/discussions)
#### Discord
@@ -33,8 +33,8 @@ Start with our comprehensive documentation:
**Best for**: Bug reports and feature requests
- [Report a bug](https://github.com/Hawksight-AI/semantica/issues/new?template=bug_report.md)
- [Request a feature](https://github.com/Hawksight-AI/semantica/issues/new?template=feature_request.md)
- [Report a bug](https://github.com/semantica-agi/semantica/issues/new?template=bug_report.md)
- [Request a feature](https://github.com/semantica-agi/semantica/issues/new?template=feature_request.md)
### Before Asking
@@ -47,7 +47,7 @@ Start with our comprehensive documentation:
### Bug Reports
Use our [bug report template](https://github.com/Hawksight-AI/semantica/issues/new?template=bug_report.md) to report bugs.
Use our [bug report template](https://github.com/semantica-agi/semantica/issues/new?template=bug_report.md) to report bugs.
Include:
- Clear description of the bug
@@ -58,7 +58,7 @@ Include:
### Feature Requests
Use our [feature request template](https://github.com/Hawksight-AI/semantica/issues/new?template=feature_request.md) to suggest features.
Use our [feature request template](https://github.com/semantica-agi/semantica/issues/new?template=feature_request.md) to suggest features.
Include:
- Problem statement
@@ -71,7 +71,7 @@ Include:
**Do NOT** create a public issue for security vulnerabilities.
Instead:
- Email: semantica-dev@users.noreply.github.com
- Email: kaif@getsemantica.ai
- Subject: [SECURITY] Brief description
- See [Security Policy](SECURITY.md) for details
@@ -79,7 +79,7 @@ Instead:
For enterprise support, custom development, or consulting:
- **Email**: semantica-dev@users.noreply.github.com
- **Email**: kaif@getsemantica.ai
- **Subject**: [ENTERPRISE] Your request
## Response Times