Skip to content

RELEASE_CHECKLIST.md

Latest commit

 

History

History
28 lines (19 loc) · 1.55 KB

RELEASE_CHECKLIST.md

File metadata and controls

28 lines (19 loc) · 1.55 KB

Ready for GitHub Publication

Use this checklist to ensure AegisScan-OpenCore is ready for a professional, ethical public release.

1. Documentation & Policy

  • README.md: Refined for "Defensive Research" tone. All "hacking" terminology removed/replaced.
  • ETHICS.md: Verify it explicitly prohibits unauthorized use and cites laws (CFAA, etc.).
  • LICENSE: Ensure AGPL-3.0 text is present in the root LICENSE file.
  • SECURITY.md: (Recommended) create a file describing how to report vulnerabilities found in the framework itself.
  • CONTRIBUTING.md: (Recommended) create guidelines that explicitly reject "exploit" submissions.

2. Code Safety Audit

  • No Exploits: Scan modules/ to ensure no actual CVE exploits (payloads) are included.
  • No Hardcoded Creds: Check for accidental API keys or passwords in examples/ or config/.
  • Clean History: Ensure .git history doesn't contain previously deleted sensitive info or aggressive tools.

3. Positioning

  • Description: GitHub repo description should match the subtitle: "Mission-Aware Defensive Adversarial Simulation Framework".
  • Topics: Use tags like: defensive-security, purple-team, adversarial-simulation, cyber-range, research.
  • NOT Tags: Avoid tags like hacking, exploit-db, malware.

4. Final Sanity Check

  • Author Identity: Ensure your git config (user.name, user.email) is what you want public.
  • Build Check: Does the Installation command actually work on a fresh machine?