‹ UPTECH Realty Pro — Real Estate Website, CRM & Rental ManagementQuality report QR-26-00117
UPTECH Realty Pro — Real Estate Website, CRM & Rental Management
Single-agency real estate suite: property website, sales CRM, rentals and tenant/landlord portal.
- Product ID
- B0408-54392
- Builder
- Uptechture Soft
- Version reviewed
- 1.0.0 · released 11 Nov 2026
- Stack
- ASP.NET Core 10 API + Angular 21 web app · C# on .NET 10 + TypeScript 5.9 · SQL Server 2019 or newer (Express, Developer, Standard, Enterprise) or Azure SQL
- Built with
- Claude Code
- Review period
- 9 Nov 2026 – 11 Nov 2026
- ✓AI code audit6 checks · 9 Nov 2026
- ✓Installed & run11 Nov 2026
- ✓Demo vs delivered11 Nov 2026
- ✓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.
- !21 of 26 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 79/100 with no failing check.
- !3 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 a placeholder, test fixture, variable name or type declaration; no real keys, connection strings or signing secrets were found. The only concern is a well-known demo password (and a default admin email) set in the shipped appsettings.json and seed.sql, which is safe only if demo mode stays off in production. | 90 | Warning |
| Dependency vulnerabilities | The Angular project pins every dependency to an exact version, ships a package-lock.json, and uses overrides to force patched transitive packages. The .NET side reportedly uses NuGet lock files and audit via Directory.Build.props, but those files and the csproj were not in the excerpt, so they could not be verified. No known critical vulnerability was identified. | 88 | Pass |
| Authorisation & access control | The digest omitted every controller and service file, so the policies, [Authorize] attributes and ownership checks on id lookups could not be traced. What is visible looks sound: role groups that mirror API policies, a rotating refresh token, a generated first-admin password and Identity-style password hashing. Several risks remain unconfirmed, so the score is capped at warning. | 70 | Warning |
| Database access rules | The project uses EF Core 10 on SQL Server with migrations, a generated idempotent schema.sql and an InitialCreate migration, which is a solid base. The digest does not include any service or query code, and the migration and schema contents are cut off, so I found no injection path but could not confirm it. Raw-SQL use, delete/update scoping, FK indexes and cascade rules are unverified. | 78 | Warning |
| Code structure & duplication | The backend is split into per-feature folders (Contacts, Leads, Leases, Cheques and so on), each with contracts, service and controller files, and the frontend mirrors that with feature folders and shared pickers and charts. The visible excerpts show clear separation, though some services and demo builders may be large and the excerpt does not show their full length. | 90 | Pass |
| Build reproducibility | The project has a pinned SDK (global.json), lock files, exact npm versions, Dockerfiles and a documented run order (user-secrets, migrations, Angular build into wwwroot/app). I could not read HowToSetup.md, the Dockerfiles, or the csproj files in the digest, so some claims are unverified. The remaining gaps are small. | 84 | Pass |
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 a placeholder, test fixture, variable name or type declaration; no real keys, connection strings or signing secrets were found. The only concern is a well-known demo password (and a default admin email) set in the shipped appsettings.json and seed.sql, which is safe only if demo mode stays off in production.
The digest omitted every controller and service file, so the policies, [Authorize] attributes and ownership checks on id lookups could not be traced. What is visible looks sound: role groups that mirror API policies, a rotating refresh token, a generated first-admin password and Identity-style password hashing. Several risks remain unconfirmed, so the score is capped at warning.
The project uses EF Core 10 on SQL Server with migrations, a generated idempotent schema.sql and an InitialCreate migration, which is a solid base. The digest does not include any service or query code, and the migration and schema contents are cut off, so I found no injection path but could not confirm it. Raw-SQL use, delete/update scoping, FK indexes and cascade rules are unverified.
Requirement list
What the builder agreed to deliver before uploading — 21 of 26 met.
- Complete source for every part Partial
- No real credentials Met
- Single example config file Met
- Database creates from empty Partial
- HowToSetup.md with two targets Met
- Pinned dependencies with lockfiles Met
- Role-protected endpoints Partial
- Working demo with sample data Partial
- Five differentiating features present in code Partial
- README.md with screenshots and licence note Met
- CLAUDE.md architecture guide (nice)Met
- CHANGELOG.md starting at 1.0.0 (nice)Met
- Seed data (nice)Met
- docker-compose.yml (nice)Met
- API and deployment docs (optional)Met
- README.md Met
- HowToSetup.md Met
- NET a project file Met
- a project file Met
- Angular a project file Met
- CLAUDE.md (nice)Met
- CHANGELOG.md (nice)Met
- LICENSE-NOTE.md Met
- a project file (nice)Met
- docker-compose.yml (nice)Met
- docs/ (optional)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 11 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 11 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
- None — approved on the first round.
- Sign-off: approved for sale on 11 Nov 2026 with 3 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.