How vansh28v/q-shield works
Q-SHIELD is a Next.js quantum-signature and security prototype. Its main evidenced workflow accepts an experiment request, runs quantum and signature checks with replay/threat analysis, creates telemetry, persists records, and returns the result. A separate attack endpoint simulates attacks and saves runs; authentication and event retrieval are additional API capabilities. The UI routes are present in the tree, but their runtime connections were not shown. Relationships below are limited to sampled calls and SOURCE INDEX references.
Main entry points: persistence.ts Persistence services · experiment.ts QDS experiment · simulator.ts Quantum engine · route.ts Experiment API
Components 17
API workflows
- Experiment API
app/api/security/experiment/route.ts - Attack API
app/api/security/attack/route.ts - Quantum API
app/api/quantum/simulate/route.ts - Authentication API
app/api/auth - Events API
app/api/events/route.ts
Quantum simulation
- Attack simulation
lib/quantum/attacks.ts - Quantum engine
lib/quantum/simulator.ts - Quantum primitives
lib/quantum/state.ts - Measurement and statistics
lib/quantum/measurement.ts
Security analysis
- QDS experiment
lib/security/experiment.ts - Signature verification
lib/security/signature.ts - Threat detection
lib/security/detector.ts - Replay ledger
lib/security/ledger.ts - Experiment telemetry
lib/security/telemetry.ts - Session handling
lib/security/session.ts
Persistence
- Persistence services
lib/security/persistence.ts - SQLite database
lib/security/db.ts
Connections 22
- Experiment API → QDS experiment: runs experiment
app/api/security/experiment/route.ts - Experiment API → Replay ledger: supplies ledger
app/api/security/experiment/route.ts - Experiment API → Experiment telemetry: creates telemetry
app/api/security/experiment/route.ts - Experiment API → Persistence services: saves results
app/api/security/experiment/route.ts - Attack API → Attack simulation: simulates attack
app/api/security/attack/route.ts - Attack API → Persistence services: saves run
app/api/security/attack/route.ts - Quantum API → Quantum engine: runs simulation
app/api/quantum/simulate/route.ts - Authentication API → Persistence services: manages accounts
app/api/auth/signup/route.ts - Authentication API → Session handling: sets session
app/api/auth/signup/route.ts - Events API → Persistence services: reads events
app/api/events/route.ts - QDS experiment → Quantum engine: runs QDS
lib/security/experiment.ts - QDS experiment → Signature verification: creates and verifies
lib/security/experiment.ts - QDS experiment → Threat detection: detects threats
lib/security/experiment.ts - QDS experiment → Replay ledger: checks replay
lib/security/experiment.ts - Attack simulation → Quantum engine: runs experiment
lib/quantum/attacks.ts - Attack simulation → Replay ledger: checks replay
lib/quantum/attacks.ts - Quantum engine → Quantum primitives: uses state operations
lib/quantum/simulator.ts - Quantum engine → Measurement and statistics: measures and analyzes
lib/quantum/simulator.ts - Signature verification → Quantum primitives: uses state operations
lib/security/signature.ts - Persistence services → SQLite database: reads and writes
lib/security/persistence.ts - Replay ledger → SQLite database: stores replay records
lib/security/ledger.ts - Session handling → Persistence services: resolves user
lib/security/session.ts