‹ FurnivoQuality report QR-26-00008
Furnivo
A ready-to-sell furniture store in Laravel: modern storefront, Shopify-style admin, English and Arabic RTL
- Product ID
- B0002-60298
- Builder
- Russel
- Version reviewed
- 1.0.0 · released 5 Oct 2026
- Stack
- Laravel · PHP 8.x · MySQL 8.0
- Built with
- Claude Code
- Review period
- 4 Oct 2026 – 5 Oct 2026
- ✓AI code audit6 checks · 4 Oct 2026
- ✓Installed & run5 Oct 2026
- ✓Demo vs delivered5 Oct 2026
- ✓Final sign-off5 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 API keys, private keys, or database credentials were found in the codebase. All .env files are examples with placeholders. One weak default exists: the demo admin password '[hidden]' in a project file ships to buyers and should be randomized or removed. | 95 | Warning |
| Dependency vulnerabilities | Both composer.lock and package-lock.json are present with exact versions. The secret scan document explicitly states '0 vulnerabilities' from dependency audit. All production dependencies are pinned to specific versions with no wildcards or pre-release tags. | 100 | Pass |
| Authorisation & access control | All admin routes are protected by auth:admin middleware and role-checked via AuthorizeAdminArea. Storefront mutating endpoints require authentication. However, several read endpoints (order view, return view, customer addresses) lack ownership verification, allowing ID enumeration to access other users' data. | 92 | Warning |
| Database access rules | All queries use parameterized statements or Eloquent ORM—no SQL injection paths detected. Foreign keys and cascades are properly defined. However, ProductBulkActions::delete() lacks a WHERE clause (deletes all products if given an empty array), and several foreign key columns lack indexes (product_id, category_id, brand_id on various tables). | 92 | Warning |
| Code structure & duplication | The codebase follows Laravel conventions well with clear service/action layers separating business logic from controllers. However, there are several oversized files (ProductController, OrderController), duplicated validation logic across request classes, and some hard-coded values that should be configuration. The architecture is maintainable but could be optimized. | 78 | Warning |
| Build reproducibility | The project is well-structured with committed lockfiles, coherent Docker setup, and clear prerequisites. HowToSetup.md covers all major paths (VPS, Docker, local). Minor issues: the Docker first-run automation isn't explicitly documented, the .env.example→.env copy step for Docker is implicit, and the setup document doesn't mention running migrations/seeders for the local path before seeding. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
No API keys, private keys, or database credentials were found in the codebase. All .env files are examples with placeholders. One weak default exists: the demo admin password '[hidden]' in a project file ships to buyers and should be randomized or removed.
All admin routes are protected by auth:admin middleware and role-checked via AuthorizeAdminArea. Storefront mutating endpoints require authentication. However, several read endpoints (order view, return view, customer addresses) lack ownership verification, allowing ID enumeration to access other users' data.
All queries use parameterized statements or Eloquent ORM—no SQL injection paths detected. Foreign keys and cascades are properly defined. However, ProductBulkActions::delete() lacks a WHERE clause (deletes all products if given an empty array), and several foreign key columns lack indexes (product_id, category_id, brand_id on various tables).
The codebase follows Laravel conventions well with clear service/action layers separating business logic from controllers. However, there are several oversized files (ProductController, OrderController), duplicated validation logic across request classes, and some hard-coded values that should be configuration. The architecture is maintainable but could be optimized.
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 5 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 5 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 5 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.