‹ CyberArena AI: Hands-On Cybersecurity Training PlatformQuality report QR-26-00076
CyberArena AI: Hands-On Cybersecurity Training Platform
Gamified cybersecurity training platform for schools, bootcamps and corporate security-awareness programs
- Product ID
- B0507-20472
- Builder
- MD MUZAHIDUL ISLAM
- Version reviewed
- 1.0.0 · released 27 Oct 2026
- Stack
- TanStack Start 1.168 (React 19) · TypeScript 5.8 · PostgreSQL 12+
- Built with
- Lovable
- Review period
- 20 Oct 2026 – 27 Oct 2026 · 2 rounds of changes
- ✓AI code audit6 checks · 20 Oct 2026
- ✓Installed & run27 Oct 2026
- ✓Demo vs delivered27 Oct 2026
- ✓Final sign-off27 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.
- ✓15 of 15 promised items delivered (setup guide, example config and the rest).
- !Security scored 71/100.
- !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 | The demo account password '[hidden]' is hardcoded in two files and documented in setup guides. While not a real credential leak, this weak default ships to buyers and must be changed before production deployment. No API keys, private keys, or database credentials were found in the codebase. | 75 | Warning |
| Dependency vulnerabilities | The project has a bun.lock lockfile and package.json with pinned versions. No known critical vulnerabilities detected in the declared dependencies. However, several packages are outdated (React 19.2.0, TanStack Router 1.170.41, Vite 8.1.5) and should be updated to their latest stable versions for security patches and bug fixes. | 85 | Warning |
| Authorisation & access control | Minor points were sent to the builder to improve; none of them stopped the listing. | 45 | Fail |
| Database access rules | No SQL injection or unscoped deletes found. All queries use parameterized statements via Supabase client or Drizzle ORM. Schema is complete and can be created from empty with proper RLS policies. However, foreign key columns lack indexes (user_id in training_progress, user_id in user_roles) which will cause performance issues as data grows. No ON DELETE CASCADE rules defined, requiring manual cleanup. | 92 | Warning |
| Code structure & duplication | The codebase has reasonable module boundaries but contains duplicated auth/environment logic across multiple files, hard-coded demo credentials in source, and a few oversized components. The game-data.ts file mixes content, validation, and command parsing. These issues are maintainable but should be refactored before scaling. | 72 | Warning |
| Build reproducibility | The project is fully reproducible with clear manifests, consistent dependencies, and proper exclusions. HowToSetup.md provides comprehensive instructions but lacks explicit Node.js/Bun version requirements and could clarify the database migration sequence. All package references resolve correctly and the Docker setup is coherent. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
The project has a bun.lock lockfile and package.json with pinned versions. No known critical vulnerabilities detected in the declared dependencies. However, several packages are outdated (React 19.2.0, TanStack Router 1.170.41, Vite 8.1.5) and should be updated to their latest stable versions for security patches and bug fixes.
No SQL injection or unscoped deletes found. All queries use parameterized statements via Supabase client or Drizzle ORM. Schema is complete and can be created from empty with proper RLS policies. However, foreign key columns lack indexes (user_id in training_progress, user_id in user_roles) which will cause performance issues as data grows. No ON DELETE CASCADE rules defined, requiring manual cleanup.
The demo account password '[hidden]' is hardcoded in two files and documented in setup guides. While not a real credential leak, this weak default ships to buyers and must be changed before production deployment. No API keys, private keys, or database credentials were found in the codebase.
The codebase has reasonable module boundaries but contains duplicated auth/environment logic across multiple files, hard-coded demo credentials in source, and a few oversized components. The game-data.ts file mixes content, validation, and command parsing. These issues are maintainable but should be refactored before scaling.
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
- .env.example 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 27 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 27 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
- Round 1: changes requested on 22 Oct 2026; the builder fixed them and uploaded again.
- Sign-off: approved for sale on 27 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.