‹ BookPointQuality report QR-26-00001
BookPoint
Booking app for your salon and spa
- Product ID
- B0001-33023
- Builder
- X1980 Group
- Version reviewed
- 1.0.0 · released 4 Oct 2026
- Stack
- Laravel · PHP 8.x · MySQL 8.0
- Built with
- Claude Code
- Review period
- 4 Oct 2026 – 4 Oct 2026
- ✓AI code audit6 checks · 4 Oct 2026
- ✓Installed & run4 Oct 2026
- ✓Demo vs delivered4 Oct 2026
- ✓Final sign-off4 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 93/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 | No committed real secrets detected. The .env.example ships with all sensitive fields empty (APP_KEY, DB_PASSWORD, ADMIN_PASSWORD, AWS_*, MAIL_PASSWORD) and explicit warnings that seeding stops without ADMIN_PASSWORD. However, several weak placeholder values could mislead buyers: DB_USERNAME='root', DB_DATABASE='bookpoint', MAIL_FROM_ADDRESS='hello@example.com'. These should be more obviously placeholder values to prevent accidental production use. | 95 | Warning |
| Dependency vulnerabilities | composer.lock is present and pins Laravel 13.17.0 (latest stable) with PHP 8.3 requirement. No known critical vulnerabilities detected. All production dependencies are pinned to specific versions. Dev dependencies (PHPUnit, Mockery) are also current. | 95 | Pass |
| Authorisation & access control | All mutating routes require authentication and role checks are enforced via middleware. Password hashing uses bcrypt. API keys are hashed and validated. The main gaps are missing ownership checks on a few client-facing read endpoints (receipts, reviews) where a client could view another client's data by changing an ID in the URL. | 92 | Warning |
| Database access rules | No SQL injection paths found—all queries use Eloquent or parameter binding. No unscoped deletes or updates on user data. The multi-tenant scope (BelongsToBusiness) is consistently applied. Schema migrations are complete and can build from empty. Minor warnings: several foreign key columns lack indexes (client_id, staff_id, service_id on bookings/payments/reviews), which will slow joins and lookups as data grows. | 92 | Warning |
| Code structure & duplication | The codebase follows Laravel conventions well with clear controller→service→model boundaries. However, several utility files are growing large (bookpoint.js at 140+ lines, helpers.php with many functions), and there is some duplicated validation and business logic across booking operations. A few hard-coded values should move to config. | 78 | Warning |
| Build reproducibility | The Laravel project is fully reproducible with composer.lock committed and clear setup steps. Docker compose references an .env file that must be manually created from an example, which is documented but could be clearer. The main setup document correctly sequences all steps including database creation. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
No committed real secrets detected. The .env.example ships with all sensitive fields empty (APP_KEY, DB_PASSWORD, ADMIN_PASSWORD, AWS_*, MAIL_PASSWORD) and explicit warnings that seeding stops without ADMIN_PASSWORD. However, several weak placeholder values could mislead buyers: DB_USERNAME='root', DB_DATABASE='bookpoint', MAIL_FROM_ADDRESS='hello@example.com'. These should be more obviously placeholder values to prevent accidental production use.
All mutating routes require authentication and role checks are enforced via middleware. Password hashing uses bcrypt. API keys are hashed and validated. The main gaps are missing ownership checks on a few client-facing read endpoints (receipts, reviews) where a client could view another client's data by changing an ID in the URL.
No SQL injection paths found—all queries use Eloquent or parameter binding. No unscoped deletes or updates on user data. The multi-tenant scope (BelongsToBusiness) is consistently applied. Schema migrations are complete and can build from empty. Minor warnings: several foreign key columns lack indexes (client_id, staff_id, service_id on bookings/payments/reviews), which will slow joins and lookups as data grows.
The codebase follows Laravel conventions well with clear controller→service→model boundaries. However, several utility files are growing large (bookpoint.js at 140+ lines, helpers.php with many functions), and there is some duplicated validation and business logic across booking operations. A few hard-coded values should move to config.
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
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 4 Oct 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 4 Oct 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 4 Oct 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.