‹ Rently MarketplaceQuality report QR-26-00127
Rently Marketplace
Peer-to-peer and operator-owned rental marketplace with customer, member and admin portals on .NET 10 and SQL Server.
- Product ID
- B0004-11361
- Builder
- CodeHarbor
- Version reviewed
- 1.0.0 · released 12 Nov 2026
- Stack
- ASP.NET Core 10 MVC (server-rendered Razor, no SPA) · C# on .NET 10 · Microsoft SQL Server 2019+ (ADO.NET, parameterised SQL, no EF)
- Built with
- Claude Code
- Review period
- 12 Nov 2026 – 12 Nov 2026
- ✓AI code audit6 checks · 11 Nov 2026
- ✓Installed & run12 Nov 2026
- ✓Demo vs delivered12 Nov 2026
- ✓Final sign-off12 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.
- !20 of 24 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 77/100 with no failing check.
- !4 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 live API keys, private keys or real connection strings were found. appsettings.json uses Trusted_Connection with no password, and Stripe/SMTP/SMS secrets are stored encrypted via the admin portal. The docker-compose file ships predictable fallback SA and app passwords, and the demo account password is documented publicly. | 88 | Warning |
| Dependency vulnerabilities | The project uses NuGet central package management (Directory.Packages.props) with lockfiles enabled and locked-mode restore, and the README states a clean NuGet audit on 11 Nov 2026. The digest does not include the actual package versions or lockfile contents, so I cannot independently verify there are no vulnerable or pre-release packages. The demo page loads React from unpkg, which is an unpinned-looking external dependency worth checking. | 82 | Pass |
| Authorisation & access control | The visible code uses bcrypt (work factor 12), server-side session validation, separate staff and user cookies, rate-limited login, and a safe returnUrl check. Only the admin AuthController and the shared middleware were visible. The 20+ admin controllers, member/customer controllers and the webhook were not shown, so guards and ownership checks on id lookups cannot be confirmed. | 72 | Warning |
| Database access rules | The visible SQL uses parameters (e.g. the login-attempt insert and the failed-login update), and CLAUDE.md states ListQuery allow-lists columns. The one string-interpolated statement only injects a table name chosen from a boolean. The schema.sql, seed.sql, Db.cs and ListQuery.cs were not in the digest, so foreign keys, indexes, cascade rules and ownership scoping could not be verified. | 72 | Warning |
| Code structure & duplication | The project follows a clear module layout (Areas per portal, Services, Security, Infrastructure), which a buyer can navigate. However, the digest shows many 'Support' partial files and large controllers that mix concerns, and some configuration and demo values are hard-coded rather than set in configuration. | 78 | Warning |
| Build reproducibility | The tree has a solution file, central package management, lock files, global.json, Dockerfile and compose, and the docs describe the steps coherently. HowToSetup.md, Dockerfile, csproj and Directory.Packages.props contents were not provided, so prerequisite ordering and version consistency could not be fully verified. Minor risks exist around the committed lock file and the tests folder. | 84 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
No live API keys, private keys or real connection strings were found. appsettings.json uses Trusted_Connection with no password, and Stripe/SMTP/SMS secrets are stored encrypted via the admin portal. The docker-compose file ships predictable fallback SA and app passwords, and the demo account password is documented publicly.
The project follows a clear module layout (Areas per portal, Services, Security, Infrastructure), which a buyer can navigate. However, the digest shows many 'Support' partial files and large controllers that mix concerns, and some configuration and demo values are hard-coded rather than set in configuration.
The visible SQL uses parameters (e.g. the login-attempt insert and the failed-login update), and CLAUDE.md states ListQuery allow-lists columns. The one string-interpolated statement only injects a table name chosen from a boolean. The schema.sql, seed.sql, Db.cs and ListQuery.cs were not in the digest, so foreign keys, indexes, cascade rules and ownership scoping could not be verified.
The visible code uses bcrypt (work factor 12), server-side session validation, separate staff and user cookies, rate-limited login, and a safe returnUrl check. Only the admin AuthController and the shared middleware were visible. The 20+ admin controllers, member/customer controllers and the webhook were not shown, so guards and ownership checks on id lookups cannot be confirmed.
Requirement list
What the builder agreed to deliver before uploading — 20 of 24 met.
- Complete source for both portals Met
- No real credentials Met
- One example config file Partial
- Database schema creates from empty Met
- Pinned dependencies with lockfile Met
- HowToSetup.md for two targets Partial
- Role-gated admin and ownership checks Partial
- Reachable demo with sample data Partial
- The five differentiating features exist (nice)Met
- CLAUDE.md for AI tools (nice)Met
- Seed data and docker-compose (nice)Met
- Keep files small and layered (nice)Met
- Optional documentation (optional)Met
- README.md Met
- HowToSetup.md Met
- NET a project file Met
- NET a project file Met
- a project file Met
- CLAUDE.md (nice)Met
- CHANGELOG.md (nice)Met
- a project file (nice)Met
- docker-compose.yml (nice)Met
- LICENSE-NOTE.md 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 12 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 12 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 12 Nov 2026 with 4 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.