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
fix: security hardening and SCM metadata updates (#1)
- Remove template placeholders from SECURITY.md (security issue)
- Replace {{OWNER}}/{{REPO}} with hyperpolymath/eclipse-ssg
- Remove PGP section (not configured)
- Update project name from template-repo to eclipse-ssg in all SCM files
- Add ADR-002 for MCP Hub Integration decision
- Add comprehensive roadmap (v0.1 to v1.0)
- Update development practices with Deno tooling
- Track resolved issues in STATE.scm
Co-authored-by: Claude <noreply@anthropic.com>
We take security seriously. We appreciate your efforts to responsibly disclose vulnerabilities and will make every effort to acknowledge your contributions.
22
4
23
5
## Table of Contents
@@ -40,7 +22,7 @@ We take security seriously. We appreciate your efforts to responsibly disclose v
40
22
41
23
The preferred method for reporting security vulnerabilities is through GitHub's Security Advisory feature:
42
24
43
-
1. Navigate to [Report a Vulnerability](https://github.com/{{OWNER}}/{{REPO}}/security/advisories/new)
25
+
1. Navigate to [Report a Vulnerability](https://github.com/hyperpolymath/eclipse-ssg/security/advisories/new)
44
26
2. Click **"Report a vulnerability"**
45
27
3. Complete the form with as much detail as possible
46
28
4. Submit — we'll receive a private notification
@@ -52,27 +34,6 @@ This method ensures:
52
34
- Coordinated disclosure tooling
53
35
- Automatic credit when the advisory is published
54
36
55
-
### Alternative: Encrypted Email
56
-
57
-
If you cannot use GitHub Security Advisories, you may email us directly:
58
-
59
-
|||
60
-
|---|---|
61
-
|**Email**| {{SECURITY_EMAIL}} |
62
-
|**PGP Key**|[Download Public Key]({{PGP_KEY_URL}})|
0 commit comments