‹ Hotel ManagerQuality report QR-26-00053
Hotel Manager
Room booking, seasonal rates, check-in/out and guest folios for small hotels and guest houses
- Product ID
- B0344-22364
- Builder
- Infymerce
- Version reviewed
- 1.0.0 · released 23 Oct 2026
- Stack
- Laravel 13 + Filament 5 · PHP 8.3+ · MySQL 8 / MariaDB 10.6+ or SQLite
- Built with
- OpenAI Codex, Claude Code, Cursor, GitHub Copilot
- Review period
- 20 Oct 2026 – 23 Oct 2026 · 1 round of changes
- ✓AI code audit6 checks · 20 Oct 2026
- ✓Installed & run23 Oct 2026
- ✓Demo vs delivered23 Oct 2026
- ✓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 96/100 with no failing check.
- !5 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 | All sensitive configuration is properly externalized to environment variables. The .env.example file contains only placeholders and instructions. Database passwords, admin passwords, and API keys are all loaded from environment variables with clear documentation. | 100 | Pass |
| Dependency vulnerabilities | All dependency manifests and lockfiles are present. No known critical vulnerabilities detected in the installed versions. A few packages could be updated to latest versions, but all are within safe ranges. The project uses stable releases with proper version pinning in lockfiles. | 85 | Warning |
| Authorisation & access control | All admin routes are protected by Filament's authentication and policies. Public booking requests are rate-limited and validated. The guest folio page (/stay/{reservation}) uses a signed URL but does not verify the guest owns that reservation—any signed link works for any reservation. Passwords are hashed with bcrypt. No unguarded admin or mutating endpoints found. | 95 | Warning |
| Database access rules | No SQL injection or unscoped deletes found. All queries use Eloquent or safe bindings. Schema has proper foreign keys with cascades. Missing indexes on several foreign key columns (room_type_id, guest_id, reservation_id) and date range queries (check_in/check_out) that will slow down availability searches and reporting as data grows. | 92 | Warning |
| Code structure & duplication | The codebase demonstrates solid architectural patterns with clear service layer separation and policy-based authorization. However, there is some duplication in validation logic across controllers, hard-coded configuration values scattered in code, and a few oversized resource classes that could benefit from refactoring. | 78 | Warning |
| Build reproducibility | The project can be built from source with Docker or locally, but HowToSetup.md has ordering issues and omissions. The Docker setup works but certificate instructions are vague. Local setup mentions seeding but doesn't clarify when demo data loads versus production admin-only. The composer setup script references npm but package-lock shows audit vulnerabilities that should be addressed. | 72 | Warning |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
All dependency manifests and lockfiles are present. No known critical vulnerabilities detected in the installed versions. A few packages could be updated to latest versions, but all are within safe ranges. The project uses stable releases with proper version pinning in lockfiles.
The codebase demonstrates solid architectural patterns with clear service layer separation and policy-based authorization. However, there is some duplication in validation logic across controllers, hard-coded configuration values scattered in code, and a few oversized resource classes that could benefit from refactoring.
All admin routes are protected by Filament's authentication and policies. Public booking requests are rate-limited and validated. The guest folio page (/stay/{reservation}) uses a signed URL but does not verify the guest owns that reservation—any signed link works for any reservation. Passwords are hashed with bcrypt. No unguarded admin or mutating endpoints found.
No SQL injection or unscoped deletes found. All queries use Eloquent or safe bindings. Schema has proper foreign keys with cascades. Missing indexes on several foreign key columns (room_type_id, guest_id, reservation_id) and date range queries (check_in/check_out) that will slow down availability searches and reporting as data grows.
The project can be built from source with Docker or locally, but HowToSetup.md has ordering issues and omissions. The Docker setup works but certificate instructions are vague. Local setup mentions seeding but doesn't clarify when demo data loads versus production admin-only. The composer setup script references npm but package-lock shows audit vulnerabilities that should be addressed.
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 23 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 23 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
- Round 1: changes requested on 22 Oct 2026; the builder fixed them and uploaded again.
- Sign-off: approved for sale on 23 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.