Institutional Attendance Platform

Attendance, leave and fiscal-calendar reporting for a public institution, hardened for production.

Role

Full-stack engineer across web, backend, infrastructure and mobile

Stack

Django
DRF
PostgreSQL
React
Vite
TypeScript
Flutter
Firebase
Pandas
ReportLab

Evidence

Commits: 95
Repositories: 4

The problem

What this had to solve.

An existing attendance system had accumulated correctness bugs in exactly the places that matter: leave balances against the Nepali fiscal calendar, Bikram Sambat date handling, and pagination that misreported record counts. It also had credentials in places they should never have been.

What I built

My contribution.

01
Standardised attendance, employee, leave, calendar, dashboard, report, profile and authentication workflows across the web application.
02
Fixed fiscal-calendar leave balances, Bikram Sambat date handling, record-count pagination, employee registration, JWT refresh and employee self-service permissions.
03
Secured reset codes, administrative APIs, biometric log ingestion and Firebase credentials, and published a sanitised Git history.
04
Prepared reproducible backend builds, production network and volume configuration, credential rotation, secret checks and a production-connected Flutter client.

The hard part

Removing secrets that are already in history

Credentials committed once are in every clone forever; deleting the file in a new commit changes nothing. The cleanup meant rewriting history, rotating every exposed credential on the assumption it was already compromised, validating the rewritten history against a separate copy before publishing, and then adding secret scanning so the next one gets caught at commit time rather than in an audit.