‹ Portfolio or Branding Website with Full CMS (Drag and Drop System) for Developers, Entrepreneur, Startup & DesignersQuality report QR-26-00150

Portfolio or Branding Website with Full CMS (Drag and Drop System) for Developers, Entrepreneur, Startup & Designers
Next.js 16 company and portfolio site with a built-in /cms admin and 22-block drag-and-drop page builder.
- Product ID
- B0097-87306
- Builder
- MD FAHIM
- Version reviewed
- 1.0.0 · released 20 Nov 2026
- Stack
- Next.js 16 (App Router) with React 19 · TypeScript 6 on Node.js 22.12+ · PostgreSQL 15+ (Prisma 7, driver adapter @prisma/adapter-pg)
- Built with
- Claude Code, Google Antigravity
- Review period
- 8 Nov 2026 – 20 Nov 2026 · 2 rounds of changes
- ✓AI code audit6 checks · 8 Nov 2026
- ✓Installed & run19 Nov 2026
- ✓Demo vs delivered20 Nov 2026
- ✓Final sign-off20 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.
- !10 of 15 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 77/100 with no failing check.
- !5 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 | Every regex candidate is either a placeholder, an environment variable reference or ordinary code handling secrets at runtime. No live API keys, private keys or real connection strings were found in the digest. A few weak, predictable defaults (demo user password, local Postgres password) ship to buyers and should be hardened or clearly flagged. | 88 | Warning |
| Dependency vulnerabilities | A pnpm-lock.yaml (297 KB) is committed and CLAUDE.md prescribes `pnpm install --frozen-lockfile`, which is good practice. However, package.json and the lockfile contents were not included in the digest, so installed versions could not be checked against advisories. The stack (Next.js 16, Prisma 7, next-auth@5, which is still a beta/pre-release line) carries pre-release and pin-range risk that the buyer should verify. | 72 | Warning |
| Authorisation & access control | Documentation describes capability-based RBAC with authorize()/requirePermission() on every write and CMS page, ownership scoping on collections, and Auth.js with hashed passwords. The digest did not include any route handlers, server actions, guards or rbac.ts, so these claims could not be traced and are not confirmed. Several visible items (edge proxy cookie-only check, public media file route, default demo credentials) need verification or tightening. | 70 | Warning |
| Database access rules | The project says it uses Prisma query methods only, with raw SQL limited to tagged templates, soft deletes and role-gated deletes by id. The digest shows none of the actual queries, schema.prisma or migration SQL, so no injection or unscoped delete was confirmed. Migration timestamps and the committed seed data are concerns a buyer would notice. | 72 | Warning |
| Code structure & duplication | The digest shows a clear layered layout: blocks, CMS modules, server actions, auth guards and storage adapters are separated, and CLAUDE.md documents the boundaries. The main structural costs are very large seed scripts and a committed 1.1 MB SQL dump duplicating the seed data, which a buyer will have to maintain. | 84 | Pass |
| Build reproducibility | The digest shows a coherent pnpm/Prisma/Docker setup with lockfile, migrations, entrypoints and documented env vars. However, the package.json, Dockerfile, HowToSetup.md body and pnpm-workspace.yaml were not visible, and generated storage media and a large seed.mjs are committed, so a clean-machine build cannot be fully confirmed. | 72 | Warning |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
Every regex candidate is either a placeholder, an environment variable reference or ordinary code handling secrets at runtime. No live API keys, private keys or real connection strings were found in the digest. A few weak, predictable defaults (demo user password, local Postgres password) ship to buyers and should be hardened or clearly flagged.
A pnpm-lock.yaml (297 KB) is committed and CLAUDE.md prescribes `pnpm install --frozen-lockfile`, which is good practice. However, package.json and the lockfile contents were not included in the digest, so installed versions could not be checked against advisories. The stack (Next.js 16, Prisma 7, next-auth@5, which is still a beta/pre-release line) carries pre-release and pin-range risk that the buyer should verify.
Documentation describes capability-based RBAC with authorize()/requirePermission() on every write and CMS page, ownership scoping on collections, and Auth.js with hashed passwords. The digest did not include any route handlers, server actions, guards or rbac.ts, so these claims could not be traced and are not confirmed. Several visible items (edge proxy cookie-only check, public media file route, default demo credentials) need verification or tightening.
The digest shows a coherent pnpm/Prisma/Docker setup with lockfile, migrations, entrypoints and documented env vars. However, the package.json, Dockerfile, HowToSetup.md body and pnpm-workspace.yaml were not visible, and generated storage media and a large seed.mjs are committed, so a clean-machine build cannot be fully confirmed.
The project says it uses Prisma query methods only, with raw SQL limited to tagged templates, soft deletes and role-gated deletes by id. The digest shows none of the actual queries, schema.prisma or migration SQL, so no injection or unscoped delete was confirmed. Migration timestamps and the committed seed data are concerns a buyer would notice.
Requirement list
What the builder agreed to deliver before uploading — 10 of 15 met.
- Complete source for every component Partial
- No real credentials in the archive Met
- Builds from a clean machine Partial
- 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
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 19 Nov 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 20 Nov 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 13 Nov 2026; the builder fixed them and uploaded again.
- Sign-off: approved for sale on 20 Nov 2026 with 5 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.