AgencyDesk — quality report QR-26-00075 | Vibe96

‹ AgencyDeskQuality report QR-26-00075

AgencyDesk
Vibe96 quality report

AgencyDesk

Client portal and agency workspace for creative, design, marketing and digital agencies

Product ID
B0001-93354
Builder
Max code
Version reviewed
1.4.0 · released 27 Oct 2026
Stack
Laravel 13.34.0 · PHP 8.3+ · MySQL 8.0+ or MariaDB 10.6+
Built with
Claude Code
Review period
26 Oct 2026 – 27 Oct 2026
83out of 100 Passed with 3 warningsPass mark 75 and no failing check.

Scores

Security84
Code structure84
Docs & completeness80
Dependency health90
Build & deploy72
  1. AI code audit6 checks · 26 Oct 2026
  2. Installed & run27 Oct 2026
  3. Demo vs delivered27 Oct 2026
  4. Final sign-off27 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.
  • 12 of 15 promised items delivered (setup guide, example config and the rest).
  • Security scored 84/100 with no failing check.
  • 3 open warnings — explained in part 1.
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.

CheckWhat we foundScoreResult
Secrets & credentialsAll six regex candidates are false positives: they are variable names, Laravel Password broker calls and a mail string, not credentials. .env.example uses empty or placeholder values, and no committed .env, keys or keystores appear in the digest. The one weak default is the demo seed's public password 'password', which is documented and guarded against production use.93Pass
Dependency vulnerabilitiesThe only manifest is composer.json, with a committed composer.lock (309 KB). Direct dependencies are pinned to exact versions, and composer is configured to block insecure and fail on abandoned packages. I found no known critical vulnerabilities in the declared versions, but the PHP requirement conflicts with the declared stack and the lockfile contents were not visible.90Pass
Authorisation & access controlThe visible code uses hashed passwords, a two-step login, an own() ownership helper that returns 404 across agencies and clients, and tenancy scopes (visibleTo). However, a project file, the middleware bodies and most controllers were not in the digest, so route-level guards on mutating and admin endpoints could not be traced. The score is capped until those can be confirmed.80Warning
Database access rulesThe visible code uses Eloquent, validated requests and visibleTo() scopes with an own() ownership check (404 across agency, client or unassigned project). The migrations include dedicated foreign key and query index files, but the digest omits the models, services and migrations, so scoping on deletes and updates, raw SQL and N+1 paths could not be confirmed. The score is capped for that gap.80Warning
Code structure & duplicationThe digest shows a clear split between controllers, services, support classes and form requests, with the largest controller at 142 lines and no god files. Some structural nits remain, such as duplicated admin and portal controller logic and a few values that belong in configuration.84Pass
Build reproducibilityThe manifest, lockfile, Dockerfile, compose and migrations are all present, and dependencies are pinned. However the declared PHP floor conflicts across files (8.3+ declared vs ^8.4 in composer.json), and HowToSetup.md was not visible, so prerequisite and step order could not be confirmed.72Warning

Open warnings

Problems that did not stop the listing. They stay on the product page until a later version fixes them.

Warning 1 Authz design looks solid, but a project file and most controllers were not visible, so it can't be fully verified

The visible code uses hashed passwords, a two-step login, an own() ownership helper that returns 404 across agencies and clients, and tenancy scopes (visibleTo). However, a project file, the middleware bodies and most controllers were not in the digest, so route-level guards on mutating and admin endpoints could not be traced. The score is capped until those can be confirmed.

Warning 2 No injection seen in the visible code, but the DB layer could only be partly verified from the digest

The visible code uses Eloquent, validated requests and visibleTo() scopes with an own() ownership check (404 across agency, client or unassigned project). The migrations include dedicated foreign key and query index files, but the digest omits the models, services and migrations, so scoping on deletes and updates, raw SQL and N+1 paths could not be confirmed. The score is capped for that gap.

Warning 3 Mostly reproducible; PHP version inconsistencies and an unverified setup document

The manifest, lockfile, Dockerfile, compose and migrations are all present, and dependencies are pinned. However the declared PHP floor conflicts across files (8.3+ declared vs ^8.4 in composer.json), and HowToSetup.md was not visible, so prerequisite and step order could not be confirmed.

Requirement list

What the builder agreed to deliver before uploading — 12 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 Partial
  • Pinned dependencies without critical CVEs (nice)Partial
  • Documentation set (nice)Met
  • Working live demo Partial
  • 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
Part 2

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 27 Oct 2026

A reviewer installed the product on a clean machine, following only the guide that ships with it.

QuestionAnswerReviewer's note
Packages restored without errorsYes
Solution builds cleanYes
Database created from the shipped script or migrationsYes
First sign-in works with the documented stepsYes
Setup guide is accurate and completeYes
Every module in the feature list opens and worksYes
No real secrets in the archiveYes
Branding and company details can be changed without codeYes

Stage 2 — Live demo compared with the delivered code

Completed 27 Oct 2026

A second reviewer checked that what the listing and demo show is what the buyer receives.

QuestionAnswerReviewer's note
Demo URL is reachableYes
Demo credentials workYes
Demo runs the same version as the archiveYes
All five differentiators are visible in the demoYes
Screenshots match the demoYes
Nothing in the demo is missing from the codeYes
Datasheet claims are accurateYes

Changes asked for during review

  • None — approved on the first round.
  • Sign-off: approved for sale on 27 Oct 2026 with 3 warnings shown publicly.

What this report covers — and what it doesn't

  • It covers version 1.4.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

ReportVersionDateScoreStatus
QR-26-000751.4.027 Oct 202683Current
QR-26-000201.0.06 Oct 202690Replaced

Vibe96 FZ-LLC, Dubai, UAE. This report describes the product at the time of review and is not a warranty.