PetPlex – Pet Grooming Booking & Adoption Platform — quality report QR-26-00142 | Vibe96

‹ PetPlex – Pet Grooming Booking & Adoption PlatformQuality report QR-26-00142

PetPlex – Pet Grooming Booking & Adoption Platform
Vibe96 quality report

PetPlex – Pet Grooming Booking & Adoption Platform

Self-hosted grooming booking and pet adoption platform with customer, staff and admin panels for pet care businesses.

Product ID
B0864-53146
Builder
Md Shijan Ali
Version reviewed
1.0.0 · released 17 Nov 2026
Stack
Next.js 15 (frontend) + Express 5 (API) · TypeScript 5.9 (Node.js 22 LTS) · PostgreSQL 16 with Prisma 7 ORM
Built with
Claude Code, Cursor, Lovable, v0 by Vercel
Review period
2 Nov 2026 – 17 Nov 2026 · 4 rounds of changes
79out of 100 Passed with 5 warningsPass mark 75 and no failing check.

Scores

Security77
Code structure84
Docs & completeness67
Dependency health78
Build & deploy80
  1. AI code audit6 checks · 2 Nov 2026
  2. Installed & run17 Nov 2026
  3. Demo vs delivered17 Nov 2026
  4. Final sign-off17 Nov 2026

At a glance

  • Installed and run from the delivered code — 6 of 8 checks answered yes.
  • Live demo compared with the delivered code — 7 of 7 checks answered yes.
  • 10 of 15 promised items delivered (setup guide, example config and the rest).
  • Security scored 77/100 with no failing check.
  • 5 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 & credentialsAll regex candidates are placeholders, env references or test fixtures; no live API keys, tokens or private keys were found in the visible files. The main concern is docker-compose falling back to a guessable Postgres password ('petplex') if the buyer doesn't set one, plus a few weak example defaults.88Warning
Dependency vulnerabilitiesBoth backend and frontend have package-lock.json files and no wildcard or 'latest' versions. All dependencies use caret ranges, and several version specifiers look unusual or could not be verified from the digest. The lockfiles' installed versions were not visible, so no known critical vulnerability could be confirmed.78Warning
Authorisation & access controlThe backend declares access (auth, permission, validation) per route through createModuleRouter, and a route-access test exists. Passwords are hashed with bcrypt and refresh tokens are stored as hashes. Only the auth routes were visible in the digest, so most of the 174 endpoints and their ownership checks could not be confirmed.72Warning
Database access rulesThe backend uses Prisma 7 with a schema split per domain, migrations and a a project file export, and the visible auth schema has foreign keys with cascade rules and indexes. The digest cuts off before any service, queryBuilder, raw SQL or migration file, so I could not confirm there are no string-built queries or unscoped deletes. The score is capped for that missing evidence, plus a few schema gaps visible in auth.prisma.72Warning
Code structure & duplicationThe project follows a consistent module structure on both sides (backend modules with route/controller/service/validation files, frontend features and views separated), and the CLAUDE.md documents conventions. The visible issues are modest: a hard-coded demo URL appears in configuration examples and the sample env, and the frontend has a large number of similar admin pages that likely repeat CRUD scaffolding.84Pass
Build reproducibilityTwo independent apps (Next.js frontend, Express/Prisma backend) have manifests, lockfiles, Dockerfiles, compose and env examples that look coherent. HowToSetup.md and several backend files (prisma/, src/config) were not visible in the digest, so some steps cannot be fully verified. A few gaps would trip a clean-machine setup: unpinned runtime versions, a postinstall hook that needs Prisma config, and a mixed zod/ESLint stack.80Warning

Open warnings

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

Warning 1 No real credentials found; weak default DB password fallbacks ship in docker-compose

All regex candidates are placeholders, env references or test fixtures; no live API keys, tokens or private keys were found in the visible files. The main concern is docker-compose falling back to a guessable Postgres password ('petplex') if the buyer doesn't set one, plus a few weak example defaults.

Warning 2 Authz design is sound, but only the auth module's routes could be verified; the rest is unreviewable

The backend declares access (auth, permission, validation) per route through createModuleRouter, and a route-access test exists. Passwords are hashed with bcrypt and refresh tokens are stored as hashes. Only the auth routes were visible in the digest, so most of the 174 endpoints and their ownership checks could not be confirmed.

Warning 3 Prisma-based access looks sound, but the digest excludes the service files and migrations needed to verify most checks

The backend uses Prisma 7 with a schema split per domain, migrations and a a project file export, and the visible auth schema has foreign keys with cascade rules and indexes. The digest cuts off before any service, queryBuilder, raw SQL or migration file, so I could not confirm there are no string-built queries or unscoped deletes. The score is capped for that missing evidence, plus a few schema gaps visible in auth.prisma.

Warning 4 Lockfiles present for both apps; caret ranges and a few version/pinning concerns, no confirmed critical CVE

Both backend and frontend have package-lock.json files and no wildcard or 'latest' versions. All dependencies use caret ranges, and several version specifiers look unusual or could not be verified from the digest. The lockfiles' installed versions were not visible, so no known critical vulnerability could be confirmed.

Warning 5 Largely reproducible monorepo; a few unverifiable steps and minor inconsistencies in setup

Two independent apps (Next.js frontend, Express/Prisma backend) have manifests, lockfiles, Dockerfiles, compose and env examples that look coherent. HowToSetup.md and several backend files (prisma/, src/config) were not visible in the digest, so some steps cannot be fully verified. A few gaps would trip a clean-machine setup: unpinned runtime versions, a postinstall hook that needs Prisma config, and a mixed zod/ESLint stack.

Requirement list

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

  • Complete source for every component Partial
  • 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 17 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 completeNo
Every module in the feature list opens and worksYes
No real secrets in the archiveYes
Branding and company details can be changed without codeNo

Stage 2 — Live demo compared with the delivered code

Completed 17 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

  • None — approved on the first round.
  • Sign-off: approved for sale on 17 Nov 2026 with 5 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.