How lina77b/secrets_vault works
SecVault is a Django web app for encrypted personal and team secrets. A signed-in user reaches account and vault routes, then can create, manage, or reveal secrets; reveal decrypts the value and records an audit event. Workspace membership and roles govern shared access, while administrators manage members and secrets. The graph includes the documented browser interactions and the main persistence, encryption, and audit layers. Some template and settings wiring is not excerpted, so relationships not evidenced by the shown source or README are omitted.
Main entry points: views.py Request handlers · audit.py Audit writer · urls.py Vault routes · models.py Secret records
Components 13
Web interface
- Vault routes
vault/urls.py - Request handlers
vault/views.py - Secret controls
static/js/app.js - Page templates
templates
Vault and sharing
- Input forms
vault/forms.py - Workspace access
vault/views.py - Secret records
vault/models.py
Security and audit
- Encryption
vault/crypto.py - Audit writer
vault/audit.py - Auth event logging
vault/signals.py - Audit history
vault/views.py
Persistence
- Database
Other components
- User
Connections 13
- User → Vault routes: uses
README.md - Vault routes → Request handlers: dispatches
vault/urls.py - Request handlers → Page templates: renders
vault/views.py - Request handlers → Input forms: validates with
vault/views.py - Request handlers → Workspace access: checks access
vault/views.py - Request handlers → Secret records: queries and saves
vault/views.py - Request handlers → Audit writer: writes events
vault/views.py - Secret controls → Request handlers: requests reveal
README.md - Secret records → Encryption: encrypts and decrypts
vault/models.py - Auth event logging → Audit writer: logs auth events
vault/signals.py - Audit writer → Database: writes logs
vault/audit.py - Request handlers → Database: queries records
vault/views.py - Audit history → Database: queries history
vault/views.py