BookPoint — quality report QR-26-00059 | Vibe96

‹ BookPointQuality report QR-26-00059

BookPoint
Vibe96 quality report

BookPoint

Complete salon, spa and clinic booking software: online booking with deposits, calendar etc in one Laravel app

Product ID
B0001-33023
Builder
Ibrahim Abdurahman
Version reviewed
1.1.0 · released 23 Oct 2026
Stack
Laravel · PHP 8.x · MySQL 8.0
Built with
Claude Code
Review period
23 Oct 2026 – 23 Oct 2026
82out of 100 Listed after a manual reviewPass mark 75 and no failing check.

Scores

Security76
Code structure78
Docs & completeness100
Dependency health95
Build & deploy92
  1. AI code audit6 checks · 23 Oct 2026
  2. Installed & run23 Oct 2026
  3. Demo vs delivered23 Oct 2026
  4. Final sign-off23 Oct 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.
  • 15 of 15 promised items delivered (setup guide, example config and the rest).
  • Security scored 76/100.
  • 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 & credentialsNo real production credentials found. However, the demo seeder and tour files contain hardcoded demo passwords ('Demo@2026') that ship to buyers. The docker-compose.yml uses empty defaults for sensitive variables, and .env.example contains placeholder values that could be mistaken for real ones. These are acceptable for a demo/development product but should be documented as requiring change before production use.92Warning
Dependency vulnerabilitiesThe project uses Laravel 13.17 with a committed composer.lock (242 KB). All dependencies are pinned to exact versions. Laravel 13.x is the latest major version (released late 2024). No known critical vulnerabilities detected in the declared packages. Minor: the project could benefit from running `composer update` to pull the latest patch releases, but the current versions are acceptable for production.95Pass
Authorisation & access controlMinor points were sent to the builder to improve; none of them stopped the listing.45Fail
Database access rulesAll queries use Eloquent with a global tenant scope (BelongsToBusiness) that prevents cross-business data leaks. No raw SQL injection or unscoped deletes found. Migrations define foreign keys with proper cascades. However, several foreign key columns lack explicit indexes (Laravel creates them for constrained() but not for manual foreignId()->constrained()), which may cause slow joins on large tables.92Warning
Code structure & duplicationThe project has clean module boundaries with services handling business logic well, but contains notable duplication in API key handling, password reset flows, and client authentication. A few files exceed comfortable maintenance thresholds. Hard-coded values are mostly confined to config files, though some magic strings appear in views.78Warning
Build reproducibilityThe project is fully reproducible: composer.lock pins all dependencies, .env.example covers all settings, and both manual and Docker paths work. The setup document could be clearer about creating the database before migrate and about the scheduler requirement, but these are standard Laravel steps.92Pass

Open warnings

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

Warning 1 Weak demo credentials and placeholder secrets in documentation

No real production credentials found. However, the demo seeder and tour files contain hardcoded demo passwords ('Demo@2026') that ship to buyers. The docker-compose.yml uses empty defaults for sensitive variables, and .env.example contains placeholder values that could be mistaken for real ones. These are acceptable for a demo/development product but should be documented as requiring change before production use.

Warning 2 Moderate code duplication and some oversized files; structure generally sound

The project has clean module boundaries with services handling business logic well, but contains notable duplication in API key handling, password reset flows, and client authentication. A few files exceed comfortable maintenance thresholds. Hard-coded values are mostly confined to config files, though some magic strings appear in views.

Warning 3 Database access rules: solid tenant scoping, minor schema gaps (missing indexes on FKs)

All queries use Eloquent with a global tenant scope (BelongsToBusiness) that prevents cross-business data leaks. No raw SQL injection or unscoped deletes found. Migrations define foreign keys with proper cascades. However, several foreign key columns lack explicit indexes (Laravel creates them for constrained() but not for manual foreignId()->constrained()), which may cause slow joins on large tables.

Requirement list

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

  • Complete source for every component Met
  • No real credentials in the archive Met
  • Builds from a clean machine Met
  • Database script or migrations Met
  • Authentication and roles on every mutating endpoint Met
  • Pinned dependencies without critical CVEs (nice)Met
  • Documentation set (nice)Met
  • Working live demo Met
  • 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 23 Oct 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 23 Oct 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 23 Oct 2026 with 3 warnings shown publicly.

What this report covers — and what it doesn't

  • It covers version 1.1.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.

Report history

ReportVersionDateScoreStatus
QR-26-000591.1.023 Oct 202682Current
QR-26-000011.0.04 Oct 202692Replaced

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