‹ Roofline CRM – Real Estate CRM with Viewing CalendarQuality report QR-26-00082
Roofline CRM – Real Estate CRM with Viewing Calendar
Real estate CRM for small agencies: listings, contacts, pipeline, calendar, follow-ups, admin/agent roles.
- Product ID
- B0183-57316
- Builder
- Redowan Ahmed Farhan
- Version reviewed
- 1.0.0 · released 29 Oct 2026
- Stack
- React 19.3.1 + Hono 4.13.13 · TypeScript 6.0.3 · PostgreSQL 17
- Built with
- Claude Code
- Review period
- 23 Oct 2026 – 29 Oct 2026 · 1 round of changes
- ✓AI code audit6 checks · 23 Oct 2026
- ✓Installed & run28 Oct 2026
- ✓Demo vs delivered29 Oct 2026
- ✓Final sign-off29 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.
- !13 of 15 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 94/100 with no failing check.
- !2 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 real credentials found. The .env.example file uses 'change-me' placeholders correctly. However, test fixtures use weak predictable passwords ('[hidden]') and the demo setup uses a hardcoded test password ('brightwater-demo'). These are acceptable for development but should be documented as test-only values. | 95 | Warning |
| Dependency vulnerabilities | All dependencies are properly pinned in pnpm-lock.yaml with exact versions. No known critical vulnerabilities detected in the production dependency tree. A few packages are slightly outdated (React 19.3.1 vs 19.3.2, Hono 4.13.13 vs 4.13.14) but these are minor version differences with no security implications. | 95 | Pass |
| Authorisation & access control | All 47 API routes are registered with explicit access rules in a central registry (a project file) and enforced by a gate middleware. Authentication, role checks, and record-level ownership are implemented via SQL helpers. Minor gap: demo mode allows password-free login for demo accounts, which is acceptable for the stated demo use case but should be clearly documented. | 95 | Pass |
| Database access rules | All queries use Drizzle's query builder with bound parameters—no SQL injection risk. Delete and update statements properly scope to agency/user via WHERE clauses. Schema has comprehensive foreign keys with sensible cascades. However, several foreign key columns lack indexes (e.g. contacts.ownerId, leads.contactId, viewings.propertyId), which will cause performance issues as data grows. | 92 | Warning |
| Code structure & duplication | Module boundaries are clean with clear separation between server, web, and shared concerns. Business logic is appropriately placed in service layers. However, some utility files exceed recommended size, and there is minor duplication in demo data generation and password handling patterns. | 82 | Pass |
| Build reproducibility | The project is well-structured with consistent dependencies and a clear build process. Package.json, lockfile, and Docker setup are coherent. HowToSetup.md provides comprehensive instructions but has minor gaps: it doesn't explicitly mention Node.js version requirement (22.12.0+) upfront, and the Docker Compose database setup could be clearer about the .env dependency. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
No real credentials found. The .env.example file uses 'change-me' placeholders correctly. However, test fixtures use weak predictable passwords ('[hidden]') and the demo setup uses a hardcoded test password ('brightwater-demo'). These are acceptable for development but should be documented as test-only values.
All queries use Drizzle's query builder with bound parameters—no SQL injection risk. Delete and update statements properly scope to agency/user via WHERE clauses. Schema has comprehensive foreign keys with sensible cascades. However, several foreign key columns lack indexes (e.g. contacts.ownerId, leads.contactId, viewings.propertyId), which will cause performance issues as data grows.
Requirement list
What the builder agreed to deliver before uploading — 13 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 Partial
- 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)Missing
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 28 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 29 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 29 Oct 2026 with 2 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.