‹ EvsntGateQuality report QR-26-00013
EvsntGate
Single-event ticketing with reserved seating, QR tickets and gate scanning for conferences and shows
- Product ID
- B0006-44111
- Builder
- Build Nest
- Version reviewed
- 1.0.0 · released 6 Oct 2026
- Stack
- ASP.NET Core 10 Blazor Server · C# 12 (.NET 10) · SQL Server 2019+
- Built with
- OpenAI Codex, 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.
- !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 committed API keys, passwords, or connection strings with real credentials were found. The production configuration correctly requires all secrets via environment variables. However, the development appsettings file generates a signing key automatically when empty, which could lead to weak keys in staging environments if not properly configured. | 92 | Warning |
| Dependency vulnerabilities | The project uses .NET 10.0.12 packages (Microsoft.EntityFrameworkCore.SqlServer, .Design, .Tools) which are current as of late 2024. No lockfile is present, but .NET projects typically rely on NuGet's package resolution and the SDK version. No known critical vulnerabilities detected in the declared dependencies. Minor concern: .NET 10 is a preview/RC version; production should use LTS releases like .NET 8. | 95 | Pass |
| Authorisation & access control | All mutating endpoints and admin routes require authentication and role checks. Payment webhooks correctly verify signatures instead of session auth. Demo login feature exposes test passwords in non-production environments. A few admin read endpoints (customer detail, order detail) lack explicit ownership checks but are protected by role requirements. | 92 | Warning |
| Database access rules | All queries use parameterized EF Core; no SQL injection paths found. Delete and update operations are properly scoped by event/order/user. The schema script is complete and creates all tables with foreign keys. However, several foreign key columns lack explicit indexes (EF Core creates them for navigation properties but not all FKs are indexed), which could impact performance on larger datasets. | 92 | Warning |
| Code structure & duplication | The architecture cleanly separates Domain, Business, Data, and Web layers with well-defined repository abstractions. Business logic stays out of Razor components. However, some service classes are large (EmailComposer, PaymentGatewayBase), and email/payment webhook handling has duplicated validation patterns. A few hard-coded values exist in configuration-sensitive areas. | 78 | Warning |
| Build reproducibility | The solution structure is clean with consistent .NET 10 references and proper project dependencies. All referenced projects exist in the archive. The setup document covers prerequisites and database creation, but lacks explicit .NET SDK version specification and could clarify the order of environment variable configuration versus first run. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
All mutating endpoints and admin routes require authentication and role checks. Payment webhooks correctly verify signatures instead of session auth. Demo login feature exposes test passwords in non-production environments. A few admin read endpoints (customer detail, order detail) lack explicit ownership checks but are protected by role requirements.
The architecture cleanly separates Domain, Business, Data, and Web layers with well-defined repository abstractions. Business logic stays out of Razor components. However, some service classes are large (EmailComposer, PaymentGatewayBase), and email/payment webhook handling has duplicated validation patterns. A few hard-coded values exist in configuration-sensitive areas.
No committed API keys, passwords, or connection strings with real credentials were found. The production configuration correctly requires all secrets via environment variables. However, the development appsettings file generates a signing key automatically when empty, which could lead to weak keys in staging environments if not properly configured.
All queries use parameterized EF Core; no SQL injection paths found. Delete and update operations are properly scoped by event/order/user. The schema script is complete and creates all tables with foreign keys. However, several foreign key columns lack explicit indexes (EF Core creates them for navigation properties but not all FKs are indexed), which could impact performance on larger datasets.
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 Met
- Pinned dependencies without critical CVEs (nice)Partial
- 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 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.