-
-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
enhancementNew feature or requestNew feature or request
Description
Is your feature request related to a problem? Please describe.
The current project would benefit from being split out into a dedicated, clean, modular repository that implements a robust cyberattack detection framework. This will improve maintainability, enable cleaner extensibility, and allow for better application of best practices (PEP 8, security, input validation, API design, etc).
Describe the solution you'd like
- Initialize a new repository (suggested name:
cyberattack-framework
or similar) focused on core detection, preprocessing, model management, REST API, and extensibility. - Move core logic (preprocessing, model training/evaluation, inference, data validation, etc.) to
src/
. - Use Flask for the API layer, with input validation (Marshmallow) and security best practices (rate limiting, JWT, etc.).
- Provide modular structure:
api/
,core/
,models/
,tests/
,data/
, and clear config separation. - Add sample notebooks and scripts for training/evaluation.
- Include CI/CD, code quality, and security checks by default.
- Update README with new usage and contribution guidelines.
Describe alternatives you've considered
- Refactoring in-place, but a fresh repo provides cleaner separation and easier future maintenance.
Additional context
- See the current
CyberAttackDetection-Python
repository for initial logic and structure inspiration. - The new repo should be PEP 8 compliant, with clear docstrings, robust error handling, and best practices for API and ML workflow security.
Copilot and canstralian
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request