Longer-term tools, scripts, and security projects built by Sheba Protocol members β individually or in small groups. This is where sustained, multi-week/month work lives, as opposed to daily logs or one-off CTF challenges.
- House real, ongoing security tools/projects (scanners, automation scripts, dashboards, research tooling)
- Give members a place to build portfolio-worthy work with proper version history
- Support collaborative projects with more than one contributor, unlike the personal-folder repos
Sheba-protocol-Project-Activity/
βββ README.md
βββ projects/
βββ network-recon-toolkit/
β βββ README.md
β βββ src/
β βββ ...
βββ phishing-detector/
β βββ README.md
β βββ ...
βββ alice-vuln-scanner/
βββ README.md
βββ ...
- Each project gets its own folder with its own
README.mdβ treat each like a mini-repo - Name folders after the project, not the person (unless it's a solo personal tool β then
<name>-<project>is fine)
Every project folder should have its own README.md:
# <Project Name>
**Author(s):**
**Status:** Planning / In Progress / Complete / Archived
**Category:** Automation / Detection / Offensive Tooling / Dashboard / Research
## What it does
Short description of the project's purpose.
## Tech stack
-
## How to run it
```bash
# setup / usage commands- [ ]
- [ ]
Anything else worth knowing β known limitations, design decisions, etc.
---
## π·οΈ Labels (for Issues β feature requests, bugs, roadmap items)
| Label | Use |
|---|---|
| `planning` | Idea stage, not yet started |
| `in-progress` | Actively being built |
| `help-wanted` | Looking for a collaborator |
| `bug` | Something's broken |
| `enhancement` | New feature idea |
---
## β
Contribution Rules
- Keep each project self-contained in its own folder with its own README
- Update project status in the README as it evolves β don't let it go stale
- If a project is abandoned, mark it `Archived` rather than deleting it β it's still useful learning history
- Solo projects are welcome, but tag teammates via `help-wanted` if you want a second contributor
---
## π Related Repos
| Repo | Purpose |
|---|---|
| `Sheba-protocol-Daily-Progress-Tracker` | Daily/weekly logs and commit tracking |
| `Sheba-protocol-Write-Up-Activity` | Formal, polished writeups |
| `Sheba-protocol-Project-Activity` | *(this repo)* Longer-term tools and projects |
| `Sheba-protocol-CTF-Activity` | Live CTF and practice logs |