‹ CliniCare — Clinic Management SaaSQuality report QR-26-00106
CliniCare — Clinic Management SaaS
Multi-tenant clinic management web app for small and mid-sized private clinics, built on React and Supabase.
- Product ID
- B0308-87960
- Builder
- Jehan Ahmed
- Version reviewed
- 1.0.0 · released 6 Nov 2026
- Stack
- React 18.3.1 + Vite 6.4 + Tailwind CSS 4.3 (shadcn-style UI) · TypeScript 5.9 (React 18.3 front end) · PostgreSQL via Supabase (minimum version not stated in the digest)
- Built with
- Claude Code
- Review period
- 4 Nov 2026 – 6 Nov 2026
- ✓AI code audit6 checks · 4 Nov 2026
- ✓Installed & run6 Nov 2026
- ✓Demo vs delivered6 Nov 2026
- ✓Final sign-off6 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.
- !12 of 22 promised items delivered (setup guide, example config and the rest).
- !Security scored 70/100 with no failing check.
- !4 open warnings — explained in 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.
| Check | What we found | Score | Result |
|---|---|---|---|
| Secrets & credentials | The scan found no real API keys, private keys, or connection strings, and .env.example ships blank. The only candidates are fictional demo-mode logins on .test domains, which are public in the live demo bundle and gate no backend. The one remaining regex hit is a UI token generator, not a secret. | 90 | Warning |
| Dependency vulnerabilities | The only manifest is package.json, and package-lock.json is present. Every dependency is pinned to an exact version with no wildcards, ranges, or pre-release builds. The lockfile contents were not available for review, so transitive vulnerabilities could not be checked, and Vite 5.4 and React 18 are behind current majors. | 82 | Pass |
| Authorisation & access control | This is a client-only Vite SPA with no server routes. Access control rests on a project file and Supabase RLS (sql/migrations, a project file), and neither was included in the excerpts. The docs claim sign-in, role and clinic-scope checks on every write, but that claim could not be confirmed from the code shown. | 60 | Warning |
| Database access rules | The digest shows no SQL, migrations, or a project file contents, only file names and documentation claims. Documentation says every write checks sign-in, role and clinic scope, with RLS as the backstop, but none of this could be verified. A score above 60 would need evidence of scoped queries, foreign keys and indexes, so this is capped at a cautious warning. | 60 | Warning |
| Code structure & duplication | The project separates landing, auth, onboarding, demo, lib and UI components cleanly, and the API layer is isolated from views. However, the demo feature sprawls across many files, and the demo store core is a large mixed-concern file, with some hard-coded fictional data and seed values embedded in components. The buyer can work with it, but the structure will be harder to maintain than it needs to be. | 72 | Warning |
| Build reproducibility | package.json pins exact dependency versions, declares engines (Node >=20, npm >=10), has build/dev/preview scripts, and ships a lockfile and a blank .env.example. The live demo shows a built Vite bundle served from Netlify, so the build evidently succeeds. Gaps: duplicate SQL sources, an unlisted Supabase function setup, a missing tsconfig verification, and an unverified setup document. | 82 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
The scan found no real API keys, private keys, or connection strings, and .env.example ships blank. The only candidates are fictional demo-mode logins on .test domains, which are public in the live demo bundle and gate no backend. The one remaining regex hit is a UI token generator, not a secret.
The project separates landing, auth, onboarding, demo, lib and UI components cleanly, and the API layer is isolated from views. However, the demo feature sprawls across many files, and the demo store core is a large mixed-concern file, with some hard-coded fictional data and seed values embedded in components. The buyer can work with it, but the structure will be harder to maintain than it needs to be.
The digest shows no SQL, migrations, or a project file contents, only file names and documentation claims. Documentation says every write checks sign-in, role and clinic scope, with RLS as the backstop, but none of this could be verified. A score above 60 would need evidence of scoped queries, foreign keys and indexes, so this is capped at a cautious warning.
This is a client-only Vite SPA with no server routes. Access control rests on a project file and Supabase RLS (sql/migrations, a project file), and neither was included in the excerpts. The docs claim sign-in, role and clinic-scope checks on every write, but that claim could not be confirmed from the code shown.
Requirement list
What the builder agreed to deliver before uploading — 12 of 22 met.
- Complete web app source Partial
- No real credentials Met
- Exactly one example env file Partial
- Pinned lockfile Met
- Database schema creates from empty Partial
- Row Level Security on every table Partial
- HowToSetup.md with two targets Partial
- Reachable demo with sample data Partial
- README with features and licence note (nice)Partial
- CLAUDE.md architecture guide (nice)Partial
- CHANGELOG starting at 1.0.0 (nice)Partial
- Seed data (nice)Partial
- README.md Met
- HowToSetup.md Met
- React Web a project filee Met
- React Web a project file Met
- a project file Met
- a project file (nice)Met
- CLAUDE.md (nice)Met
- CHANGELOG.md (nice)Met
- LICENSE-NOTE.md (optional)Met
- docs/ (optional)Met
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 6 Nov 2026A reviewer installed the product on a clean machine, following only the guide that ships with it.
| Question | Answer | Reviewer's note |
|---|---|---|
| Packages restored without errors | Yes | |
| Solution builds clean | Yes | |
| Database created from the shipped script or migrations | Yes | |
| First sign-in works with the documented steps | Yes | |
| Setup guide is accurate and complete | Yes | |
| Every module in the feature list opens and works | Yes | |
| No real secrets in the archive | Yes | |
| Branding and company details can be changed without code | Yes |
Stage 2 — Live demo compared with the delivered code
Completed 6 Nov 2026A second reviewer checked that what the listing and demo show is what the buyer receives.
| Question | Answer | Reviewer's note |
|---|---|---|
| Demo URL is reachable | Yes | |
| Demo credentials work | Yes | |
| Demo runs the same version as the archive | Yes | |
| All five differentiators are visible in the demo | Yes | |
| Screenshots match the demo | Yes | |
| Nothing in the demo is missing from the code | Yes | |
| Datasheet claims are accurate | Yes |
Changes asked for during review
- None — approved on the first round.
- Sign-off: approved for sale on 6 Nov 2026 with 4 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.