‹ Next-booksQuality report QR-26-00015
Next-books
Cloud accounting for UAE SMEs: invoicing, bills, expenses, banking, FIFO inventory, VAT 201 returns and reports.
- Product ID
- B0006-96276
- Builder
- Build Nest
- Version reviewed
- 1.0.0 · released 6 Oct 2026
- Stack
- ASP.NET Core 10 MVC · C# 12 / .NET 10 · SQL Server 2019+
- Built with
- Claude Code
- Review period
- 6 Oct 2026 – 6 Oct 2026
- ✓AI code audit6 checks · 6 Oct 2026
- ✓Installed & run6 Oct 2026
- ✓Demo vs delivered6 Oct 2026
- ✓Final sign-off6 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.
- !14 of 15 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 92/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 | No real credentials were discovered in the codebase. However, docker-compose.yml references MSSQL_SA_PASSWORD from environment without a strong default, and .env.example ships empty (buyers may set weak passwords). The application correctly externalizes all secrets to appsettings.json and environment variables, which is good practice. | 92 | Warning |
| Dependency vulnerabilities | All dependency lockfiles are present and pinned. No known critical or high-severity vulnerabilities detected in the .NET packages (Dapper 2.1.35, FluentAssertions 7.0.0, xUnit 2.9.2) or npm dependencies (htmx.org 2.0.4, tailwindcss 3.4.17). Several packages are 1-2 years old but remain secure. The project uses explicit version pinning in packages.lock.json files, which is best practice. | 85 | Warning |
| Authorisation & access control | All mutating endpoints require authentication via [Authorize] and role checks via [RequirePermission]. Password hashing uses a proper hasher (PasswordHasher). The main gaps are missing ownership checks on a few read endpoints (user can query another user's sign-in history, trusted devices, or email settings by changing the userId parameter). These are low-risk but should verify the current user matches the requested userId. | 92 | Warning |
| Database access rules | All SQL is parameterized via Dapper; no string concatenation of user input. Delete and update statements are properly scoped by organization or user. Schema scripts are complete with foreign keys and cascade rules. A few foreign key columns lack indexes, which may cause performance issues under load but do not compromise security. | 92 | Pass |
| Code structure & duplication | Checked by our reviewers during the human review. | 70 | Warning |
| Build reproducibility | The solution builds cleanly with consistent .NET 10 references and proper project structure. Docker setup is complete and coherent. Minor issues: HowToSetup.md doesn't specify Node.js version requirement for npm commands, and the setup document could be clearer about when to run database scripts versus the migrate command. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
All dependency lockfiles are present and pinned. No known critical or high-severity vulnerabilities detected in the .NET packages (Dapper 2.1.35, FluentAssertions 7.0.0, xUnit 2.9.2) or npm dependencies (htmx.org 2.0.4, tailwindcss 3.4.17). Several packages are 1-2 years old but remain secure. The project uses explicit version pinning in packages.lock.json files, which is best practice.
No real credentials were discovered in the codebase. However, docker-compose.yml references MSSQL_SA_PASSWORD from environment without a strong default, and .env.example ships empty (buyers may set weak passwords). The application correctly externalizes all secrets to appsettings.json and environment variables, which is good practice.
All mutating endpoints require authentication via [Authorize] and role checks via [RequirePermission]. Password hashing uses a proper hasher (PasswordHasher). The main gaps are missing ownership checks on a few read endpoints (user can query another user's sign-in history, trusted devices, or email settings by changing the userId parameter). These are low-risk but should verify the current user matches the requested userId.
Requirement list
What the builder agreed to deliver before uploading — 14 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 Partial
- 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
- appsettings.example.json 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 6 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 6 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 6 Oct 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.