Halden House

Hotel & travel website with online booking, seven designs, English/Arabic, and full admin panel

Product ID: B0002-85513
Builder: Buildify
Version reviewed: 1.0.0 · released 19 Oct 2026
Stack: Laravel 12.69 · PHP 8.2+ · MySQL 8 / MariaDB 10.6+
Built with: Claude Code
Review period: 16 Oct 2026 – 19 Oct 2026

Download PDF View the product

88out of 100 Passed with 5 warningsPass mark 75 and no failing check.

Scores

Security93

Code structure72

Docs & completeness100

Dependency health95

Build & deploy72

AI code audit6 checks · 16 Oct 2026
Installed & run19 Oct 2026
Demo vs delivered19 Oct 2026
Final sign-off19 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.
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.

Check	What we found	Score	Result
Secrets & credentials	All credentials are properly externalized to environment variables with placeholder values in .env.example. No API keys, database passwords, or private keys are committed. The only concern is HowToSetup.md line 38 showing a demo password generation command that could be misunderstood as a production practice, though it's clearly labeled for demo mode only.	95	Warning
Dependency vulnerabilities	Both composer.lock and package-lock.json are present with pinned versions. The project documentation states a dependency audit was performed on 15 Oct 2026 with 0 npm vulnerabilities and 0 known advisories for 131 PHP packages. All production dependencies use exact versions. Minor: some packages may have newer versions available, but no security issues detected.	95	Pass
Authorisation & access control	All admin routes are protected by authentication + role middleware. Mutating endpoints require auth. However, booking detail/receipt endpoints lack ownership verification (any signed-in user can read any booking by ID), lead details are unguarded, and demo mode allows unauthenticated admin panel access when enabled. Password hashing uses bcrypt correctly.	92	Warning
Database access rules	No SQL injection or unscoped destructive queries found. All queries use parameter binding or Eloquent ORM. Schema migrations are complete with foreign keys and cascades. However, several foreign key columns lack explicit indexes (Laravel creates them automatically on constraints, but explicit indexes are clearer). A few N+1 query paths exist but are mitigated by eager loading in controllers.	92	Warning
Code structure & duplication	The Laravel application has good module separation (Cms, Support, Livewire components) and clear concerns, but contains significant duplication in database seeders, migration patterns, and admin component traits. Several files exceed 300 lines and could be split. Hard-coded values exist in configuration but are mostly documented.	72	Warning
Build reproducibility	The Laravel project can be built following HowToSetup.md, but critical details are missing: Node.js version not specified (package.json shows Node 20+ needed but HowToSetup.md omits this), Docker setup references docker.env.example that doesn't exist in the file tree, and the setup document doesn't verify database creation before migration. The composer.json platform constraint locks PHP 8.2.12 but .env.example and docs say 8.2+, creating version ambiguity.	72	Warning

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 demo password generation in setup docs needs attention

All credentials are properly externalized to environment variables with placeholder values in .env.example. No API keys, database passwords, or private keys are committed. The only concern is HowToSetup.md line 38 showing a demo password generation command that could be misunderstood as a production practice, though it's clearly labeled for demo mode only.

Warning 2 Authorization mostly solid; missing ownership checks on booking/lead reads and demo mode bypass

All admin routes are protected by authentication + role middleware. Mutating endpoints require auth. However, booking detail/receipt endpoints lack ownership verification (any signed-in user can read any booking by ID), lead details are unguarded, and demo mode allows unauthenticated admin panel access when enabled. Password hashing uses bcrypt correctly.

Warning 3 Database access mostly safe; minor schema gaps (missing indexes on foreign keys)

No SQL injection or unscoped destructive queries found. All queries use parameter binding or Eloquent ORM. Schema migrations are complete with foreign keys and cascades. However, several foreign key columns lack explicit indexes (Laravel creates them automatically on constraints, but explicit indexes are clearer). A few N+1 query paths exist but are mitigated by eager loading in controllers.

Warning 4 Moderate code duplication and some oversized files; architecture is sound but refactoring needed

The Laravel application has good module separation (Cms, Support, Livewire components) and clear concerns, but contains significant duplication in database seeders, migration patterns, and admin component traits. Several files exceed 300 lines and could be split. Hard-coded values exist in configuration but are mostly documented.

Warning 5 Build reproducible with gaps: missing Node version, unclear Docker setup, incomplete prerequisites

The Laravel project can be built following HowToSetup.md, but critical details are missing: Node.js version not specified (package.json shows Node 20+ needed but HowToSetup.md omits this), Docker setup references docker.env.example that doesn't exist in the file tree, and the setup document doesn't verify database creation before migration. The composer.json platform constraint locks PHP 8.2.12 but .env.example and docs say 8.2+, creating version ambiguity.

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 19 Oct 2026

A 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 19 Oct 2026

A 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 19 Oct 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.