‹ FreshNestQuality report QR-26-00057
FreshNest
A ready-to-sell organic grocery store in Laravel storefront, Shopify-style admin, Stripe and cash on delivery.
- Product ID
- B0001-73574
- Builder
- Buildify
- Version reviewed
- 1.1.0 · released 23 Oct 2026
- Stack
- Laravel · PHP 8.x · MySQL 8.0
- Built with
- Claude Code
- Review period
- 23 Oct 2026 – 23 Oct 2026
- ✓AI code audit6 checks · 23 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 92/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 real credentials were found in the codebase. The .env.example file correctly uses placeholders for all sensitive values. However, the ADMIN_PASSWORD field in .env.example is left empty with instructions to generate a strong password, which is good practice but could lead to weak passwords if users ignore the guidance. | 95 | Warning |
| Dependency vulnerabilities | The project uses Tailwind CSS 4.3.3 which is a pre-release version (4.x is still in beta). Composer dependencies are pinned in composer.lock but several packages are 6-12 months old. No known critical vulnerabilities detected in the installed versions. The pre-release Tailwind and outdated packages warrant attention before production deployment. | 85 | Warning |
| Authorisation & access control | All mutating endpoints require authentication with proper guards (auth:admin, auth:web). Password storage uses bcrypt/Hash::make throughout. Role checks are enforced on sensitive admin areas. Minor gaps: traffic live endpoint lacks ownership validation (any admin sees all visitors), and tour state updates don't verify the tour belongs to the admin's accessible areas before resuming. | 92 | Warning |
| Database access rules | No SQL injection paths found. Query builders are used correctly throughout. One unscoped delete in Cleanup service could affect wrong records if called incorrectly. Schema is complete with proper foreign keys, but several foreign key columns lack indexes (traffic_sessions.user_id, order_items.product_id, etc.) which will hurt performance at scale. | 88 | Warning |
| Code structure & duplication | The project demonstrates good separation of concerns with clear module boundaries, services handling business logic, and controllers remaining thin. However, there is some duplication in validation rules, configuration values scattered across files, and a few oversized controllers that could benefit from further decomposition. | 82 | Pass |
| Build reproducibility | The project is fully reproducible with correct dependency versions, proper .gitignore exclusions, and a comprehensive setup guide. Minor issues: HowToSetup.md doesn't explicitly mention Node.js version requirement (though package.json exists), and the GeoIP database download step could be clearer about when it's needed. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
The project uses Tailwind CSS 4.3.3 which is a pre-release version (4.x is still in beta). Composer dependencies are pinned in composer.lock but several packages are 6-12 months old. No known critical vulnerabilities detected in the installed versions. The pre-release Tailwind and outdated packages warrant attention before production deployment.
No API keys, private keys, or real credentials were found in the codebase. The .env.example file correctly uses placeholders for all sensitive values. However, the ADMIN_PASSWORD field in .env.example is left empty with instructions to generate a strong password, which is good practice but could lead to weak passwords if users ignore the guidance.
No SQL injection paths found. Query builders are used correctly throughout. One unscoped delete in Cleanup service could affect wrong records if called incorrectly. Schema is complete with proper foreign keys, but several foreign key columns lack indexes (traffic_sessions.user_id, order_items.product_id, etc.) which will hurt performance at scale.
All mutating endpoints require authentication with proper guards (auth:admin, auth:web). Password storage uses bcrypt/Hash::make throughout. Role checks are enforced on sensitive admin areas. Minor gaps: traffic live endpoint lacks ownership validation (any admin sees all visitors), and tour state updates don't verify the tour belongs to the admin's accessible areas before resuming.
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
- None — approved on the first round.
- Sign-off: approved for sale on 23 Oct 2026 with 4 warnings shown publicly.
What this report covers — and what it doesn't
- It covers version 1.1.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-00057 | 1.1.0 | 23 Oct 2026 | 90 | Current |
| QR-26-00003 | 1.0.0 | 4 Oct 2026 | 91 | Replaced |
Vibe96 FZ-LLC, Dubai, UAE. This report describes the product at the time of review and is not a warranty.