How night-master/sdlc_python works
Project type and purpose
• This is a full-stack, front-end/back-end separated DevSecOps web platform (“sdlc_python”).
• Purpose: simulate common vulnerabilities for security training and perform AI-powered code audits (shift security left in SDLC).
File structure
• Top-level “sdlc_python_front” folder: Vue 3 single-page application (SPA) – components, views, router, store, assets, config, public.
• Top-level “sdlc_python_backend” folder: Flask application – app.py entrypoint, middleware, routes, utilities, vulnerability modules, SQLite database, uploads.
• “data” folder holds sample screenshots.
• Deployment: start.bat runs backend (Flask) and serves front-end (built Vue assets).
Main components
a. Client Browser (User’s web browser with SPA)
b. Front-End Application (Vue 3):
• Modules: router, state management (Vuex or Pinia), views, components, HTTP client for API calls.
• Built static assets (HTML/CSS/JS) served by web server or Flask static endpoint.
c. Back-End Application (Flask API):
• API Layer (routes/routes.py): login, vulnerability demos, code scanning endpoints.
• Middleware (authentication, request preprocessing).
• Vulnerability Simulation Modules (bac.py, xss.py, rce.py, etc.)
• Code Audit Module (integrates with large language model via utils/get_code.py)
• Utilities (database connection, JWT utils, HTTP client utils)
d. Database (SQLite test.db): stores users, sessions, scan reports.
e. File Storage (uploads directory): holds code samples for scanning, file uploads for demos.
f. External Service: Large Language Model API (for AI code audit)
Relationships and data flows
• User Browser → HTTP(S) → Vue SPA (served via Nginx/Flask)
• Vue SPA → HTTP API calls → Flask API
• Login → Flask Auth middleware → SQLite
• Fetch vulnerability demo pages → Flask static/templates
• Submit code for scan → Flask code-audit handler → LLM API → audit results → Flask returns JSON → Vue displays results
• Flask → SQLite (reads/writes users, scan results)
• Flask → File Storage (reads demo assets, writes uploads)
• Flask → External LLM API (code audit)
Architectural patterns and design principles
• Front-end/Back-end separation with RESTful API.
• Modular Flask structure:
• “middleware” layer for cross-cutting concerns (auth, logging).
• “routes” layer as controller.
• “vulnerabilities” modules as business logic.
• “utils” for shared services (DB, JWT, HTTP).
• Vue component-based UI, central state management, router guard for auth.
• Lightweight SQLite for prototype, easily replaceable with other RDBMS.
• Major components (browser, front-end, back-end, database, file store, external AI).
• Related sub-modules in each component.
• Clear, legible labels and directional flow.
• “shift-left code audit” flow: front-end → Flask → LLM → results → front-end.