Contributing
Adding material
- Choose the correct platform directory and follow its existing taxonomy.
- Identify the room, box, module, challenge, or certification track clearly.
- Prefer explanations of techniques and reasoning over copied challenge text.
- Keep commands and proof-of-concept code narrowly scoped to the exercise.
- Check links and remove local paths, usernames, tokens, and host-specific data.
Disclosure and safety
- Follow the platform's current writeup and disclosure policy.
- Do not publish spoilers for active machines, competitions, or examinations.
- Never commit flags, credentials, session cookies, VPN profiles, private keys, personal data, or access details for a live target.
- Do not submit material obtained from systems outside an authorized lab or competition scope.
Use focused commits. A commit should normally cover one room, box, module, challenge, or certification topic.
Repository maintenance
- Keep generated binaries, packet captures containing secrets, tool caches, and local editor files out of Git.
- Preserve useful history when moving content.
- Changes to the root structure should update the platform table in
README.md.