// the take
A college OOP coursework project that implements the same basic RBAC idea twice: a Next.js/TypeScript/MongoDB web app with Admin/Teacher/Student dashboards, and a separate C++ console version using SQLite for the data layer. It's aimed at students learning access-control and OOP concepts, not at anyone needing a real authorization system.
The role split (Admin/Teacher/Student) is enforced server-side via API routes and a dedicated authorization lib rather than just hidden client-side, which is the right instinct for an RBAC demo. Doing the same domain model in both TypeScript and C++ (AccessControl, AuthManager, AuditLog classes) is a genuinely useful way to show OOP principles translate across languages. The scope is intentionally small, so the whole access-control logic is readable in one sitting rather than buried in a framework.
Compiled build output is committed straight into git: CMake caches, .obj files, a .ninja_log, a built rbac.exe, and a SQLite rbac.db — that's an environment leak and will break for anyone on a different OS/compiler. There's no real automated test suite, just standalone scripts (test-authorization.ts, test-teacher.ts) that look like manual smoke tests rather than CI-run tests. Session handling, CSRF protection, and password hashing choices aren't documented or visible from the README, so you can't tell if the auth is sound without reading the code yourself. Zero stars, zero forks, and it's explicitly labeled a coursework project — there's no indication anyone besides the author has used or reviewed it.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →