‹ FurnivoQuality report QR-26-00019

Furnivo
Self-hosted Laravel ecommerce for luxury furniture with Shopify-style admin, Stripe & multi-currency
- Product ID
- B0001-65228
- Builder
- Buildify
- Version reviewed
- 1.2.0 · released 6 Oct 2026
- Stack
- Laravel 12.69 · PHP 8.2 · MySQL 8.0
- Built with
- Claude Code
- Review period
- 6 Oct 2026 – 6 Oct 2026
- ✓AI code audit6 checks · 6 Oct 2026
- ✓Installed & run6 Oct 2026
- ✓Demo vs delivered6 Oct 2026
- ✓Final sign-off6 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 95/100 with no failing check.
- !1 open warning — 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 examined files use proper placeholder values (empty strings, 'your_key_here', 'example.com') in .env.example files and configuration. Sensitive values like Stripe keys, database passwords, and API credentials are correctly loaded from environment variables. Demo passwords are generated securely at runtime and never hardcoded. | 100 | Pass |
| Dependency vulnerabilities | Both composer.lock and package-lock.json are present with exact versions pinned. The secret scan confirms 0 vulnerabilities reported in a project file. All production dependencies use stable releases with no wildcards or pre-release versions. | 100 | Pass |
| Authorisation & access control | All admin routes require authentication via auth:admin guard and role checks through AuthorizeAdminArea middleware. Mutating endpoints are properly protected. Password handling uses Laravel's Hash facade correctly. Minor gaps: LandingController serves files without authentication (by design but verify intent), and some customer-facing read endpoints lack explicit ownership checks though most are session-scoped. | 92 | Warning |
| Database access rules | All queries use Eloquent ORM or parameterized query builder methods. No SQL injection vectors found. Delete and update operations are properly scoped to authenticated users or specific IDs. Foreign keys and cascades are correctly defined. A few indexes on foreign keys could improve performance on large datasets. | 92 | Pass |
| Code structure & duplication | The application demonstrates good separation of concerns with thin controllers, business logic in services/actions, and clear module boundaries. However, there is notable duplication in theme view files (product cards, sections, modals) and seeder data structures that could be refactored. A few hard-coded values exist but are mostly confined to configuration files. | 82 | Pass |
| Build reproducibility | The project is fully reproducible: composer.json and package.json lock to specific versions, Docker setup is coherent, and HowToSetup.md walks through all prerequisites. Minor deductions for not explicitly stating MySQL 8.0+ requirement in the quick-start Docker section and the platform.php explanation being in composer.json comments rather than setup docs. | 95 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
All admin routes require authentication via auth:admin guard and role checks through AuthorizeAdminArea middleware. Mutating endpoints are properly protected. Password handling uses Laravel's Hash facade correctly. Minor gaps: LandingController serves files without authentication (by design but verify intent), and some customer-facing read endpoints lack explicit ownership checks though most are session-scoped.
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 6 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 6 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 6 Oct 2026 with 1 warning shown publicly.
What this report covers — and what it doesn't
- It covers version 1.2.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
| Report | Version | Date | Score | Status |
|---|---|---|---|---|
| QR-26-00019 | 1.2.0 | 6 Oct 2026 | 94 | Current |
| QR-26-00002 | 1.0.0 | 4 Oct 2026 | 93 | Replaced |
Vibe96 FZ-LLC, Dubai, UAE. This report describes the product at the time of review and is not a warranty.