‹ Hostinkar - Web Hosting, Domain & Billing PlatformQuality report QR-26-00097
Hostinkar - Web Hosting, Domain & Billing Platform
Hosting company platform: website, shop, billing, provisioning and support.
- Product ID
- B0868-32652
- Builder
- Raziul
- Version reviewed
- 1.0.0 · released 5 Nov 2026
- Stack
- Laravel 13 with Inertia 3 and Vue 3 · PHP 8.3+ with TypeScript (Vue 3) · MySQL 8 / MariaDB 10.6+
- Built with
- Claude Code
- Review period
- 30 Oct 2026 – 5 Nov 2026 · 1 round of changes
- ✓AI code audit6 checks · 30 Oct 2026
- ✓Installed & run5 Nov 2026
- ✓Demo vs delivered5 Nov 2026
- ✓Final sign-off5 Nov 2026
At a glance
- ✓Installed and run from the delivered code — 7 of 7 checks answered yes.
- ✓Live demo compared with the delivered code — 7 of 7 checks answered yes.
- !10 of 15 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 77/100 with no failing check.
- !5 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 | All regex candidates are placeholders, environment-variable references or PHP code (Password facade, token variables), not real secrets. The .env.example is clean, and the docker-compose.yml uses required env vars. Weak default demo logins ([email protected] / admin) ship in a project file and the README, which buyers could leave active in production. | 88 | Warning |
| Dependency vulnerabilities | The digest only shows part of composer.json and none of the lockfile contents, so no known critical vulnerability can be confirmed. Caret ranges are used for PHP packages (normal), and composer.lock and package-lock.json are said to exist but were omitted. Several dependencies are very new or pre-1.0 (laravel/chisel ^0.1.0, laravel/wayfinder ^0.1.14), which carry stability risk, and the Vite config uses 'vite-plus', an uncommon toolchain. | 70 | Warning |
| Authorisation & access control | The digest shows no route files (a project file, client.php, api.php) or policies, so per-route guards could not be traced. The documented design is solid: auth:admin, active-staff and 2FA middleware, a permission middleware on every admin route, client_id policies, hashed API tokens ([hidden]) and Fortify password hashing. A few concrete risks are visible and the demo credentials are wea | 72 | Warning |
| Database access rules | The digest shows Eloquent and a query helper (TableQuery) with whitelisted sort columns, and no string-built SQL or unscoped deletes were visible. However, only a small slice of the 1735 files was provided, so raw SQL, migrations, foreign keys and indexes could not be verified. The score is capped until the schema and the services can be reviewed. | 72 | Warning |
| Code structure & duplication | The project is organised into well-named domain modules (Admin, Billing, Catalog, Client, Api, Ai) with driver contracts and registries, which keeps boundaries readable. The digest shows a few large files and repeated patterns that a buyer will need to navigate, but nothing that looks like copy-pasted modules or dead code shipped in bulk. | 88 | Pass |
| Build reproducibility | The project has a coherent Laravel 13 + Vite layout, a compose file that requires explicit DB passwords, and a setup document covering VPS, Docker and shared hosting. A few gaps remain: unverifiable lockfiles and the setup guide, a misleading starter-kit name, and a Vite config using a non-standard toolchain. | 80 | Warning |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
All regex candidates are placeholders, environment-variable references or PHP code (Password facade, token variables), not real secrets. The .env.example is clean, and the docker-compose.yml uses required env vars. Weak default demo logins ([email protected] / admin) ship in a project file and the README, which buyers could leave active in production.
The digest shows no route files (a project file, client.php, api.php) or policies, so per-route guards could not be traced. The documented design is solid: auth:admin, active-staff and 2FA middleware, a permission middleware on every admin route, client_id policies, hashed API tokens ([hidden]) and Fortify password hashing. A few concrete risks are visible and the demo credentials are wea
The digest only shows part of composer.json and none of the lockfile contents, so no known critical vulnerability can be confirmed. Caret ranges are used for PHP packages (normal), and composer.lock and package-lock.json are said to exist but were omitted. Several dependencies are very new or pre-1.0 (laravel/chisel ^0.1.0, laravel/wayfinder ^0.1.14), which carry stability risk, and the Vite config uses 'vite-plus', an uncommon toolchain.
The project has a coherent Laravel 13 + Vite layout, a compose file that requires explicit DB passwords, and a setup document covering VPS, Docker and shared hosting. A few gaps remain: unverifiable lockfiles and the setup guide, a misleading starter-kit name, and a Vite config using a non-standard toolchain.
The digest shows Eloquent and a query helper (TableQuery) with whitelisted sort columns, and no string-built SQL or unscoped deletes were visible. However, only a small slice of the 1735 files was provided, so raw SQL, migrations, foreign keys and indexes could not be verified. The score is capped until the schema and the services can be reviewed.
Requirement list
What the builder agreed to deliver before uploading — 10 of 15 met.
- Complete source for every component Partial
- No real credentials in the archive Met
- Builds from a clean machine Partial
- Database script or migrations Met
- Authentication and roles on every mutating endpoint Partial
- Pinned dependencies without critical CVEs (nice)Partial
- Documentation set (nice)Met
- Working live demo Partial
- 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 5 Nov 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 | N/A |
Stage 2 — Live demo compared with the delivered code
Completed 5 Nov 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 5 Nov 2026 with 5 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.