// the take
A CLI-based student record manager written in a single C file, with a role-based login system (Admin/Staff/User/Guest) gating CRUD access to text-file-backed records. It's a university course project (six listed authors, campus-style student IDs) rather than a tool anyone would deploy.
Deleting a record via a temp-file swap instead of rewriting the original in place is the right call in C and avoids data loss if the program crashes mid-write. Handling full names with embedded spaces is a small thing but it's exactly the kind of scanf() bug most beginner C projects get wrong. Enforcing unique roll numbers on insert is a sensible basic integrity check.
credentials.txt is checked directly into the repo, and there's nothing in the README suggesting passwords are hashed — if they're plaintext, that's a real problem even for a toy project, and it teaches a bad habit. Everything lives in one file (SRMS.c) despite the README calling the design 'modular' — there's no separation between auth, I/O, and record logic. No build instructions, no Makefile, and text-file storage with no locking means it will corrupt under any concurrent access, which is fine for a class demo but worth knowing before anyone extends it.
We read the README, the directory tree and a key source file in September 2026. Nobody pays to be listed. How we judge →