Skip to content

Latest commit

Β 

History

4 Commits

Folders and files

NameName
Last commit message
Last commit date
Β 
Β 

Repository files navigation

πŸ› οΈ Sheba Protocol β€” Project Activity

Team Type Status

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.


🎯 Purpose

  • 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

πŸ“‚ Structure

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)

🧾 Project README Template

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

Roadmap

  • [ ]
  • [ ]

Notes

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 |

About

Ongoing tools, scripts, and longer-term security projects built by the Sheba Protocol team.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors