Dependable-clean — quality report QR-26-00118 | Vibe96

‹ Dependable-cleanQuality report QR-26-00118

Dependable-clean
Vibe96 quality report

Dependable-clean

Full-stack cleaning business platform with customer booking, staff dispatch and role-based dashboards

Product ID
B0446-53515
Builder
Nishat Raihana Prantik
Version reviewed
1.8.2 · released 11 Nov 2026
Stack
Next.js 16.2 + React 19.3 (frontend), Express 5.1 (backend) · JavaScript (Node.js 20.13+) · MongoDB 6.20+
Built with
OpenAI Codex, Claude Code, GitHub Copilot
Review period
9 Nov 2026 – 11 Nov 2026
86out of 100 Passed with 2 warningsPass mark 75 and no failing check.

Scores

Security88
Code structure84
Docs & completeness100
Dependency health88
Build & deploy80
  1. AI code audit6 checks · 9 Nov 2026
  2. Installed & run11 Nov 2026
  3. Demo vs delivered11 Nov 2026
  4. Final sign-off11 Nov 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 88/100 with no failing check.
  • 2 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 & credentialsEvery regex candidate is a variable name, a hashing call, or a test fixture, not a committed credential. a project filee uses placeholders and an empty AUTH_SECRET, and the production config refuses weak secrets. Only the visible digest was reviewed, so files omitted from it could not be checked.95Pass
Dependency vulnerabilitiesEvery dependency in the three manifests is pinned to an exact version with no wildcards or pre-release tags, and a single root package-lock.json is used for the npm workspace. The lockfile contents were not included in the digest, so the installed versions and advisories could not be verified. A few declared stack versions differ from the pinned ones, which is a minor documentation inconsistency.88Pass
Authorisation & access controlEvery visible write route uses a role guard or the rate limiter, lookups by id are scoped in the database query, and passwords use salted scrypt with revocable tokens. The digest cut off teams, reviews, services and support routes, so those could not be verified, and a few low-risk gaps remain.88Pass
Database access rulesThe MongoDB access visible in the digest is well scoped: operator keys are rejected, booking lookups put owner/assignee in the filter, and migrations add indexes and validators. Weaknesses are full-collection reads filtered in JavaScript and read-all endpoints. The digest was truncated, so team.js, reviews.js, support.js, services.js and the migrations were not seen.80Warning
Code structure & duplicationThe backend is split into one router per domain area with shared middleware, auth and validation modules, and the README and AGENTS notes describe the layout accurately. Weaknesses are some dense single-line handlers and repeated shape checks (e.g. signup/login/setup password handling, team-member and location lookups scanning full collections), plus hard-coded business values such as the 3-day lead time and the 15-minute rate-limit window that are only partly configurable.84Pass
Build reproducibilityWorkspaces, a single root lockfile, pinned versions, .nvmrc and per-package build scripts make a clean restore and build plausible. The declared stack (Next 16.2, Express 5.1, MongoDB 6.20+) differs from the pinned versions (Next 16.4.5, Express 5.2.1, driver 6.21.0), and HowToSetup.md was not in the digest, so its step order could not be verified.80Warning

Open warnings

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

Warning 1 No injection or unscoped destructive queries seen; some scans in-memory, partial review only

The MongoDB access visible in the digest is well scoped: operator keys are rejected, booking lookups put owner/assignee in the filter, and migrations add indexes and validators. Weaknesses are full-collection reads filtered in JavaScript and read-all endpoints. The digest was truncated, so team.js, reviews.js, support.js, services.js and the migrations were not seen.

Warning 2 Build mostly reproducible; HowToSetup.md unseen and version claims conflict with declared stack

Workspaces, a single root lockfile, pinned versions, .nvmrc and per-package build scripts make a clean restore and build plausible. The declared stack (Next 16.2, Express 5.1, MongoDB 6.20+) differs from the pinned versions (Next 16.4.5, Express 5.2.1, driver 6.21.0), and HowToSetup.md was not in the digest, so its step order could not be verified.

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
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 11 Nov 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 11 Nov 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 11 Nov 2026 with 2 warnings shown publicly.

What this report covers — and what it doesn't

  • It covers version 1.8.2 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-001181.8.211 Nov 202686Current
QR-26-000961.3.04 Nov 202674Replaced
QR-26-000771.0.028 Oct 20260Replaced

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