‹ AgencyDeskQuality report QR-26-00020
AgencyDesk
Client portal and agency workspace for creative, design, marketing and digital agencies
- Product ID
- B0001-93354
- Builder
- Max code
- Version reviewed
- 1.0.0 · released 6 Oct 2026
- Stack
- Laravel 13.34.0 · PHP 8.3+ · MySQL 8.0+ or MariaDB 10.6+
- Built with
- Claude Code
- Review period
- 4 Oct 2026 – 6 Oct 2026 · 1 round of changes
- ✓AI code audit6 checks · 4 Oct 2026
- ✓Installed & run5 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.
- !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 | All regex candidates are placeholders, example values, or Laravel framework defaults. The .env.example file correctly uses placeholder values and instructs users to generate keys. No real API keys, passwords, or credentials are committed. | 100 | Pass |
| Dependency vulnerabilities | composer.json pins all direct dependencies to exact versions (e.g., laravel/framework: 13.34.0). composer.lock is present with 309 KB of locked transitive dependencies. The project enforces 'composer audit --locked' in scripts and blocks insecure packages via config.audit settings. | 100 | Pass |
| Authorisation & access control | All mutating routes require authentication and proper role/permission checks via middleware. Password reset tokens and two-factor codes are properly hashed. A few read-only endpoints (file download, approval show, invoice show) lack explicit ownership verification in the controller, relying solely on Eloquent scopes which could be bypassed if the scope is removed in future refactoring. | 92 | Warning |
| Database access rules | No SQL injection or unscoped destructive queries found. All queries use Eloquent or parameter binding. Multi-tenant scoping is enforced via visibleTo() scopes and agency_id checks. Schema has proper foreign keys with cascades, but a few foreign key columns lack indexes which may impact query performance at scale. | 92 | Warning |
| Code structure & duplication | The codebase demonstrates solid architectural discipline with business logic properly isolated in Services and permission checks in Middleware. However, several controllers exceed 150 lines, there is duplicated validation logic across request classes, and some configuration values are hard-coded in controllers rather than centralized. | 78 | Warning |
| Build reproducibility | The Laravel project can be built from source with composer install and artisan commands. However, HowToSetup.md omits critical database creation steps, doesn't specify MySQL version requirements clearly, and the Docker setup lacks volume persistence configuration. The .env.example shows all required variables but setup instructions assume pre-existing database. | 72 | Warning |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
No SQL injection or unscoped destructive queries found. All queries use Eloquent or parameter binding. Multi-tenant scoping is enforced via visibleTo() scopes and agency_id checks. Schema has proper foreign keys with cascades, but a few foreign key columns lack indexes which may impact query performance at scale.
All mutating routes require authentication and proper role/permission checks via middleware. Password reset tokens and two-factor codes are properly hashed. A few read-only endpoints (file download, approval show, invoice show) lack explicit ownership verification in the controller, relying solely on Eloquent scopes which could be bypassed if the scope is removed in future refactoring.
The codebase demonstrates solid architectural discipline with business logic properly isolated in Services and permission checks in Middleware. However, several controllers exceed 150 lines, there is duplicated validation logic across request classes, and some configuration values are hard-coded in controllers rather than centralized.
The Laravel project can be built from source with composer install and artisan commands. However, HowToSetup.md omits critical database creation steps, doesn't specify MySQL version requirements clearly, and the Docker setup lacks volume persistence configuration. The .env.example shows all required variables but setup instructions assume pre-existing database.
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 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
- Round 1: changes requested on 5 Oct 2026; the builder fixed them and uploaded again.
- Sign-off: approved for sale on 6 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.