mpanaryin/job_scope
43.6
Weak · 8 November 2026
5k
lines of production code
Python
primary language
7
measurements over time
What this system is
This system is a backend application infrastructure focused on operational robustness, featuring a FastAPI service backed by PostgreSQL and Redis. It implements a comprehensive observability stack using ELK for centralized logging and Prometheus/Grafana for metrics monitoring. The architecture supports asynchronous database operations, background task processing via Celery, and secure JWT-based authentication with token revocation capabilities.
Features
Added directory structure printing utility
A new Python script, \tools/print\structure.py\, has been added to the repository. This tool allows users to print a formatted tree view of a directory structure, filtering out common non-essential files and directories (such as \\\pycache\\_\, \.git\, and \venv\) and optionally limiting the depth of displayed folders like \alembic\ or \media\. It can be run from the command line to visualize the project layout.
tools · high confidence
New centralized logging, metrics, and infrastructure organization
The \infra\ directory now houses the complete operational stack, consolidating services previously scattered in the project root. This change introduces a full ELK-based logging pipeline (Filebeat, Logstash, Elasticsearch, Kibana) that collects and parses application, Nginx, and PostgreSQL logs, including specific handling for Celery tasks and error notifications via Telegram. Additionally, a Prometheus and Grafana stack is added to monitor system, FastAPI, Nginx, and PostgreSQL metrics, with pre-configured dashboards for each. The Nginx configuration has been updated to expose internal metrics endpoints (\/\_\_internal\metrics\\_\, \/stub\_status\) and standardize log paths, while Redis and PostgreSQL configurations are now explicitly managed within this infrastructure layer.
infra · high confidence
Behavioural changes
Database migration system and authentication infrastructure overhaul
The backend now uses Alembic for database schema management, introducing initial migrations for the users and vacancies tables (including a subsequent migration to add an updated\_at column) and configuring the environment to support PostgreSQL-specific features like JSONB. Concurrently, the authentication system has been restructured to support token revocation via Redis storage and allows JWT signing to be configured via an algorithm setting (defaulting to ES256 in the codebase), replacing previous hardcoded or simpler implementations.
backend · high confidence
Log directory structure reorganized for infrastructure components
The logging directory structure has been updated to separate logs by infrastructure component. New placeholder directories have been created for FastAPI, Nginx, and PostgreSQL logs, aligning with the new organizational scheme where logs are stored in the root logs directory and partitioned by service.
logs · medium confidence
Static assets relocated to project root
Static files, including CSS stylesheets and JavaScript libraries, have been moved from the backend source directory to a dedicated static folder at the project root. This structural change separates static content from the application code, preparing the layout for external serving by nginx rather than the FastAPI backend.
static · high confidence
Dependencies
Updated backend dependencies to support PostgreSQL, async database drivers, and observability tools
The backend requirements have been expanded to include async PostgreSQL drivers (asyncpg, psycopg), Alembic for database migrations, Elasticsearch and aiohttp clients, Celery and Redis for background tasks, Prometheus instrumentation, and updated testing libraries (pytest, httpx). The aiosqlite dependency remains present but is now accompanied by the necessary stack to support PostgreSQL and enhanced logging/monitoring capabilities.
(dependencies) · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 43 → 44 (+0.3)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 75 → 75 (+0.0)
- Architecture 77 → 77 (-0.7)
- Maturity 63 → 65 (+1.9)
- Readiness 28 → 28 (+0.0)
- Security 71 → 72 (+0.8)
- Domain Modelling 80 → 80 (+0.0)
- Accessibility 40 → 40 (+0.0)
- Performance 100 → 100 (+0.0)
Resolved (1)
- Split backend
New (1)
- Projects may be oversized for their cohesion
Architecture
- Unchanged — 0 containers · 1 contexts · 0 edges
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
mpanaryin/job_scope was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 8 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit dfcc24357b41f4ec602415c9e4dba8664a1a69ee — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-45ab2cab63de.