Arcade Portal

HTML5 game portal with upload, instant play, members, comments and ads for site owners

Product ID: B0344-39004
Builder: Infymerce
Version reviewed: 1.0.0 · released 22 Oct 2026
Stack: Laravel 13 + Filament 5 · PHP 8.3+ · MySQL 8 / MariaDB 10.6+ (SQLite for evaluation)
Built with: Claude Code
Review period: 20 Oct 2026 – 22 Oct 2026

Download PDF View the product

91out of 100 Passed with 2 warningsPass mark 75 and no failing check.

Scores

Security91

Code structure82

Docs & completeness100

Dependency health95

Build & deploy92

AI code audit6 checks · 20 Oct 2026
Installed & run20 Oct 2026
Demo vs delivered22 Oct 2026
Final sign-off22 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 91/100 with no failing check.
2 open warnings — explained in part 1.

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	All sensitive values are properly externalized to environment variables via .env.example. Database passwords, admin passwords, and API keys are documented as placeholders requiring user configuration. The codebase follows Laravel best practices for credential management with no hardcoded secrets.	100	Pass
Dependency vulnerabilities	Both composer.lock and package-lock.json are present and committed. All production dependencies are pinned to specific versions with no known critical vulnerabilities. A few packages may be slightly outdated (Laravel 13.17, Filament 5.10) but these are recent stable releases with no security advisories.	95	Pass
Authorisation & access control	All admin routes are behind Filament's auth + policies (admin/staff roles). Mutations (play, like, favourite, comment, report) require member guard or rate-limit. Passwords use bcrypt. Two minor gaps: member account page shows another member's favourites/recent if you guess their ID (no route exists, but if added it would leak); no CSRF on GET-based like/favourite fallback (POST is fine).	95	Warning
Database access rules	No SQL injection vulnerabilities detected. All user input is properly parameterized through Eloquent or validated. However, several foreign key columns lack indexes (category_id, member_id, game_id in various tables), which will cause performance issues as data grows. A few delete/update operations lack explicit scoping but appear safe in context.	78	Warning
Code structure & duplication	The project demonstrates good separation of concerns with clear module boundaries (Controllers, Services, Models, Filament Resources). Business logic is appropriately placed in Services and Models. However, there is some duplication in Filament resource definitions, a few hard-coded configuration values, and some oversized resource files that could be refactored.	82	Pass
Build reproducibility	The project is fully reproducible from the archive. All dependencies resolve correctly, Docker configuration is coherent, and the setup document covers all prerequisites. Minor issues: HowToSetup.md shows database creation after .env configuration but the .env.example references DB credentials that must exist first; npm install command in composer.json scripts uses --ignore-scripts flag without explanation; demo mode environment variables are documented but their interaction with routing is not clear in setup steps.	92	Pass

Open warnings

Problems that did not stop the listing. They stay on the product page until a later version fixes them.

Warning 1 Missing foreign key indexes and some unscoped queries; no injection paths found

No SQL injection vulnerabilities detected. All user input is properly parameterized through Eloquent or validated. However, several foreign key columns lack indexes (category_id, member_id, game_id in various tables), which will cause performance issues as data grows. A few delete/update operations lack explicit scoping but appear safe in context.

Warning 2 Strong authz on admin & mutations; minor ownership gaps on member reads

All admin routes are behind Filament's auth + policies (admin/staff roles). Mutations (play, like, favourite, comment, report) require member guard or rate-limit. Passwords use bcrypt. Two minor gaps: member account page shows another member's favourites/recent if you guess their ID (no route exists, but if added it would leak); no CSRF on GET-based like/favourite fallback (POST is fine).

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

Part 2

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 20 Oct 2026

A 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 22 Oct 2026

A 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 22 Oct 2026 with 2 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.