How mrtracker-new/invisiovault works
Project Type and Purpose
• This is a two-tier full-stack application. The frontend is a React single-page application (SPA). The backend is a Flask REST API that implements steganography and polyglot file utilities.
• Purpose: Let users hide arbitrary files or text inside images (steganography mode) or create dual-format “polyglot” files (carrier + hidden payload) with optional password encryption.
File Structure
• Top-level directories:
• backend/ – Flask application
• frontend/ – React SPA
• backend/ contains:
• api/routes.py – REST endpoint definitions
• utils/ – core steganography, polyglot, validation, and cleanup logic
• config/settings.py – environment and CORS configuration
• app.py – application factory and entry point
• frontend/ contains:
• src/components – HideFile, ExtractFile, Polyglot components
• config/api.js – Axios base URL
• main.jsx & App.jsx – React entry and router
• Deployment files:
• Procfile, railway.json for backend
• vercel.json for frontend
Extract Additional Architectural Insights from README
• RESTful API design with endpoints for hide, extract, download, health check
• Two main modes of operation: steganography and polyglot
• Temporary file storage (uploads directory) and automatic cleanup
• Security features: CORS, file type/size validation, encryption modules (Fernet, AES-256)
Main Components
a. Frontend (React SPA)
• UI components for HideFile, ExtractFile, Polyglot
• HTTP client (Axios) and routing (React Router via App.jsx)
• Environment config (VITE_API_URL)
b. Backend (Flask REST API)
• API Layer (routes.py)
• Service Layer (utils steganography, polyglot, validators, cleanup)
• Configuration Layer (settings.py, .env)
• Temporary File Storage (uploads folder)
c. External Interfaces
• Browser (user)
• HTTP/HTTPS between frontend and backend
d. Data Storage & Flow
• Incoming file payload → backend → utility modules → generated file kept in uploads → returned to frontend → user downloads
e. Security & Support Services
• Encryption libraries (Cryptography, Pyzipper)
• CORS module
• Zlib for compression
Relationships and Interactions
• Browser/React SPA sends REST calls (POST /api/hide, POST /api/extract, GET /api/download/{id})
• Flask API receives request, invokes utility module, writes temp file, returns a download token or file stream
• Cleanup module removes temp files after a configured time
• React receives response, triggers file download or displays extracted text
Architectural Patterns & Design Principles
• Separation of concerns: UI vs. API vs. core logic
• Modular utility libraries (each stego/polyglot step isolated)
• Stateless HTTP endpoints (all state in temporary files)
• Environment-based configuration (12-factor)
• Security first: validation, encryption, cleanup
Details
• Every module and external dependency (e.g., Vite, Flask-CORS) is visible