‹ Tijara - Supermarket Management SystemQuality report QR-26-00027
This report has been replaced — a newer version of Tijara - Supermarket Management System was reviewed. See the current report (QR-26-00028) →
Tijara - Supermarket Management System
Complete supermarket management system for single-company grocery chains (1–50 stores) with POS, online store & delivery
- Product ID
- B0001-72066
- Builder
- Ibrahim Abdurahman
- Version reviewed
- 1.0.0 · released 7 Oct 2026
- Stack
- ASP.NET Core 9 MVC · C# 12 (.NET 9.0) · SQL Server 2019+
- Built with
- Claude Code
- Review period
- 4 Oct 2026 – 7 Oct 2026
- ✓AI code audit6 checks · 4 Oct 2026
- ✓Installed & run4 Oct 2026
- ✓Demo vs delivered4 Oct 2026
- ✓Final sign-off7 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 — 6 of 7 checks answered yes.
- ✓15 of 15 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 93/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 API keys, passwords, or connection strings with real credentials were found. The codebase correctly uses placeholders and requires secrets via environment variables or user-secrets. Two minor issues: BCrypt work factor defaults to 12 (acceptable but could be higher for 2025), and .env.example ships with empty required fields that could confuse deployment. | 95 | Warning |
| Dependency vulnerabilities | The project uses .NET 9 with NuGet packages.lock.json files committed across all projects, ensuring reproducible builds. All dependencies are pinned to specific versions. No known critical vulnerabilities detected in the declared packages, though some packages (QuestPDF 2024.10.3, Hangfire.AspNetCore 1.8.14) are slightly behind their latest stable releases. | 95 | Pass |
| Authorisation & access control | All mutating endpoints are protected by [Authorize] and role policies. Password hashing uses BCrypt with work factor 12. Authentication is cookie-based with antiforgery protection. Minor gaps: several read endpoints (product details, branch stock, customer orders) lack ownership checks allowing cross-customer/branch data access by ID manipulation. | 92 | Warning |
| Database access rules | All SQL uses parameterised queries via the Sql.cs reader helpers—no concatenation or injection paths found. Delete/update statements scope by branch/user/status correctly. Schema scripts are numbered and checksummed. Foreign keys exist on all relationships. Minor: a few high-traffic foreign keys (BranchStock.ProductID, SaleItem.ProductID) lack explicit indexes, relying on clustered PK coverage. | 92 | Pass |
| Code structure & duplication | Module boundaries are clean and business logic is properly layered. However, several controller files exceed 600 lines, repository methods show copy-paste patterns, and configuration values are scattered across multiple files rather than centralized. No dead code detected, but refactoring opportunities exist. | 72 | Warning |
| Build reproducibility | All project references resolve, SDK version is pinned (9.0.100), and packages.lock.json files are committed. Docker Compose configuration is complete and coherent. Two minor issues: HowToSetup.md references a non-existent appsettings.example.json path, and the .env.example file doesn't clarify that empty DEMO_PASSWORD_HASH values will skip demo data loading rather than fail. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
No API keys, passwords, or connection strings with real credentials were found. The codebase correctly uses placeholders and requires secrets via environment variables or user-secrets. Two minor issues: BCrypt work factor defaults to 12 (acceptable but could be higher for 2025), and .env.example ships with empty required fields that could confuse deployment.
All mutating endpoints are protected by [Authorize] and role policies. Password hashing uses BCrypt with work factor 12. Authentication is cookie-based with antiforgery protection. Minor gaps: several read endpoints (product details, branch stock, customer orders) lack ownership checks allowing cross-customer/branch data access by ID manipulation.
Module boundaries are clean and business logic is properly layered. However, several controller files exceed 600 lines, repository methods show copy-paste patterns, and configuration values are scattered across multiple files rather than centralized. No dead code detected, but refactoring opportunities exist.
Requirement list
What the builder agreed to deliver before uploading — 15 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 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
- 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 4 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 4 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 | No | |
| 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 7 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.
Report history
| Report | Version | Date | Score | Status |
|---|---|---|---|---|
| QR-26-00028 | 1.1.0 | 7 Oct 2026 | 92 | Current |
| QR-26-00027 | 1.0.0 | 7 Oct 2026 | 91 | Replaced |
Vibe96 FZ-LLC, Dubai, UAE. This report describes the product at the time of review and is not a warranty.