secutils

Bundle of security tools for pentesters, developers and compliance security engineers

Proposed tree structure. Can perfectly be modified:

We can do full Python tools. Folder c_core is a C++ based folder which can be called if you rather using more efficient algorithms/speed up processes. It is not necessary to call it. Only use it if you want to, @3v401 will add some low level tools there to speed up processes.

We don't need to stick to one folder each of us. We can jump to other folders and colaborate between us. This is just a draft.

secutils/
├─ src/
│  └─ secutils/
│     ├─ __init__.py
│     ├─ _version.py
│     ├─ _core/                 # @3v401: Low level programming tools <------------------ Your tools here
│     │  ├─ CMakeLists.txt
│     │  ├─ bindings.cpp      
│     │  └─ corelib/
│     ├─ pentest/              # @reventl0v: Pentesting tools <-------------------------- Your tools here
│     │  ├─ __init__.py
│     │  └─ XXXX.py         
│     └─ compliance/            # @al-Munqidh: Compliance tools <------------------------- Your tools here
│        ├─ __init__.py
│        └─ XXXXX.py       
├─ tests/
│  ├─ test_pentest.py          # @reventl0v: In case you want to show your tool tested in real case
│  └─ test_compliance.py        # @al-Munqidh: In case you want to show your tool tested in real case
├─ benchmarks/
│  └─ bench_XXXXX.py            # @3V401: Here we could do an energy/time/space benchmark to check whether prebuilt or our own tool is more efficient with plots
├─ examples/
│  └─ quickstart.ipynb
├─ CMakeLists.txt                
├─ pyproject.toml              
├─ README.md
├─ LICENSE
├─ CHANGELOG.md
├─ SECURITY.md
├─ CONTRIBUTING.md
├─ CODE_OF_CONDUCT.md
└─ .github/
   └─ workflows/
      └─ wheels.yml