Iyada: Clinic Booking and Patient Management — quality report QR-26-00146 | Vibe96

‹ Iyada: Clinic Booking and Patient ManagementQuality report QR-26-00146

Iyada: Clinic Booking and Patient Management
Vibe96 quality report

Iyada: Clinic Booking and Patient Management

Self-hosted English/Arabic clinic app for 1-10 doctor practices: booking, patient files, billing, insurance, queue.

Product ID
B0612-89035
Builder
Bablu Mia
Version reviewed
1.0.0 · released 18 Nov 2026
Stack
Django 6.1 + Django REST Framework 3.18, React 19 + Vite 8 + Tailwind 4 · Python 3.12 + TypeScript 6 (React 19 web app) · PostgreSQL 16 (with Redis 7 for cache and background jobs)
Built with
Claude Code
Review period
5 Nov 2026 – 18 Nov 2026 · 1 round of changes
83out of 100 Passed with 3 warningsPass mark 75 and no failing check.

Scores

Security83
Code structure88
Docs & completeness73
Dependency health82
Build & deploy80
  1. AI code audit6 checks · 5 Nov 2026
  2. Installed & run18 Nov 2026
  3. Demo vs delivered18 Nov 2026
  4. Final sign-off18 Nov 2026

At a glance

  • Installed and run from the delivered code — 8 of 8 checks answered yes.
  • Live demo compared with the delivered code — 7 of 7 checks answered yes.
  • 11 of 15 promised items delivered (setup guide, example config and the rest).
  • Security scored 83/100 with no failing check.
  • 3 open warnings — explained in part 1.
Part 1

AI code audit

The full source archive was read by our AI auditor against each check. It reads the code — it does not run it; running it is part 2.

CheckWhat we foundScoreResult
Secrets & credentialsEvery regex candidate is a form field name, an environment variable reference, or a randomly generated test value. The .env.example leaves all secrets empty and relies on an init_env command to generate them, and CI generates random values at runtime. A small residual risk remains because the full archive was not visible, notably a project file (4 MB) and the omitted files.92Pass
Dependency vulnerabilitiesThe backend pins every Python package to an exact version, and the web app has a package-lock.json that fixes its npm ranges. No known critical vulnerability could be confirmed from the visible versions. The remaining items are weaker pinning in package.json, no visible backend hash lockfile, and an unverified redis image tag.82Pass
Authorisation & access controlThe digest shows a deliberate access design: ScopedViewSet with permission codes per action, an access-matrix test, JWT with MFA, hashed-password fields and scoped API keys. Only a handful of URL files were visible, so most endpoints could not be traced, and several public/token endpoints (demo-login, display token, patient token) need ownership checks confirmed.78Warning
Database access rulesThe visible material shows a disciplined Django ORM backend. Docs state soft-delete, db_index on every FK, and encrypted ID numbers, and a test enforces permission scoping. The digest omitted all models, migrations, views and raw SQL, so none of these claims could be checked against code, and a 4 MB seed.sql plus a 347 KB schema.sql could not be checked either.80Warning
Code structure & duplicationThe backend is split into clear apps (authentication, clinic, patients, clinical, billing, and so on) and the web app into feature folders with file-size and complexity limits enforced by lint. The digest shows no god files or copy-pasted modules, though it is too partial to confirm the limits are met everywhere.88Pass
Build reproducibilityPinned dependencies, lockfile, Dockerfiles and a coherent compose file make a clean build likely. HowToSetup.md and the backend Dockerfile were not in the excerpt, so setup order and some references could not be confirmed, and a few small inconsistencies were found.80Warning

Open warnings

Problems that did not stop the listing. They stay on the product page until a later version fixes them.

Warning 1 Backend DB code was largely not visible; the conventions are strong, but the schema and queries could not be verified

The visible material shows a disciplined Django ORM backend. Docs state soft-delete, db_index on every FK, and encrypted ID numbers, and a test enforces permission scoping. The digest omitted all models, migrations, views and raw SQL, so none of these claims could be checked against code, and a 4 MB seed.sql plus a 347 KB schema.sql could not be checked either.

Warning 2 Largely reproducible build; setup doc and a few inconsistencies could not be fully verified

Pinned dependencies, lockfile, Dockerfiles and a coherent compose file make a clean build likely. HowToSetup.md and the backend Dockerfile were not in the excerpt, so setup order and some references could not be confirmed, and a few small inconsistencies were found.

Warning 3 Authz design looks solid but most views were not visible; a few unverifiable public and token endpoints

The digest shows a deliberate access design: ScopedViewSet with permission codes per action, an access-matrix test, JWT with MFA, hashed-password fields and scoped API keys. Only a handful of URL files were visible, so most endpoints could not be traced, and several public/token endpoints (demo-login, display token, patient token) need ownership checks confirmed.

Requirement list

What the builder agreed to deliver before uploading — 11 of 15 met.

  • Complete source for every component Met
  • No real credentials in the archive Met
  • Builds from a clean machine Partial
  • Database script or migrations Met
  • Authentication and roles on every mutating endpoint Partial
  • Pinned dependencies without critical CVEs (nice)Partial
  • Documentation set (nice)Met
  • Working live demo Partial
  • README.md Met
  • HowToSetup.md Met
  • CLAUDE.md (or AGENTS.md) (nice)Met
  • CHANGELOG.md (nice)Met
  • .env.example Met
  • a project file Met
  • a project file (nice)Met
Part 2

Human review

Reviewers from the Vibe96 team in Dubai worked through each question below; a final reviewer signed it off.

Stage 1 — Installed and run from the delivered code

Completed 18 Nov 2026

A reviewer installed the product on a clean machine, following only the guide that ships with it.

QuestionAnswerReviewer's note
Packages restored without errorsYes
Solution builds cleanYes
Database created from the shipped script or migrationsYes
First sign-in works with the documented stepsYes
Setup guide is accurate and completeYes
Every module in the feature list opens and worksYes
No real secrets in the archiveYes
Branding and company details can be changed without codeYes

Stage 2 — Live demo compared with the delivered code

Completed 18 Nov 2026

A second reviewer checked that what the listing and demo show is what the buyer receives.

QuestionAnswerReviewer's note
Demo URL is reachableYes
Demo credentials workYes
Demo runs the same version as the archiveYes
All five differentiators are visible in the demoYes
Screenshots match the demoYes
Nothing in the demo is missing from the codeYes
Datasheet claims are accurateYes

Changes asked for during review

  • Round 1: changes requested on 13 Nov 2026; the builder fixed them and uploaded again.
  • Sign-off: approved for sale on 18 Nov 2026 with 3 warnings shown publicly.

What this report covers — and what it doesn't

  • It covers version 1.0.0 exactly as the buyer downloads it: the source archive, the setup guide and the live demo on the dates above.
  • It is not a penetration test, a performance or load test, or a legal review of third-party package licences.
  • Scores are a point in time. Libraries age; a later version is audited again and gets its own report.
  • Your setup matters. Hosting, configuration and changes made after purchase are outside this review.
  • How the score is made: each AI check is scored 0–100 and weighted (security counts most). A listing needs 75 or more, no failing check, and the human review passed.
  • Always try the live demo before buying, and ask the builder questions from the product page.

Vibe96 FZ-LLC, Dubai, UAE. This report describes the product at the time of review and is not a warranty.