How codexeron/projects-omniscope works
OmniScope analyzes a submitted website URL and returns an eight-dimension report through either the CLI or a local web dashboard/API. The documented dimensions are represented, but several analyzer implementations and the orchestrator’s dispatch loop were not included in the excerpts; their placement in engine.py follows the README and visible class structure, while uncertain internal wiring is omitted.
Main entry points: engine.py Analysis orchestrator · omniscope.py CLI and API · script.js Dashboard client · models.py Report model
Components 18
User Interfaces
- CLI and API
omniscope.py - Dashboard page
templates/index.html - Dashboard client
static/script.js
Analysis Runtime
- URL validation
engine.py - Analysis orchestrator
engine.py - Page fetch
engine.py
Analysis Dimensions
- Performance
engine.py - Security and TLS
engine.py - SEO
engine.py - Accessibility
engine.py - Best practices
engine.py - Eco score
engine.py - Broken links
engine.py - Mobile friendly
engine.py
Report Output
- Report model
models.py
Other components
- User
- Target website
- Linked pages
Connections 20
- User → CLI and API: submits URL
- CLI and API → Dashboard page: serves page
- Dashboard page → Dashboard client: loads client
- Dashboard client → CLI and API: requests analysis
- CLI and API → URL validation: validates URL
- CLI and API → Analysis orchestrator: starts analysis
- Analysis orchestrator → Page fetch: fetches page
- Page fetch → Target website: requests page
- Analysis orchestrator → Performance: analyzes context
- Analysis orchestrator → Security and TLS: analyzes context
- Analysis orchestrator → SEO: analyzes context
- Analysis orchestrator → Accessibility: analyzes context
- Analysis orchestrator → Best practices: analyzes context
- Analysis orchestrator → Eco score: analyzes context
- Analysis orchestrator → Broken links: analyzes context
- Analysis orchestrator → Mobile friendly: analyzes context
- Broken links → Linked pages: checks links
- Analysis orchestrator → Report model: assembles report
- CLI and API → Report model: returns report
- Dashboard client → Report model: renders response