‹ InventraQuality report QR-26-00033
Inventra
Multi-warehouse inventory & purchasing system for UAE/GCC traders and contractors
- Product ID
- B0006-33270
- Builder
- Build Nest
- Version reviewed
- 1.0.0 · released 9 Oct 2026
- Stack
- Laravel 12.69 · PHP 8.2 · Microsoft SQL Server 2017+ (primary), MySQL 8 / MariaDB 10.3+
- Built with
- OpenAI Codex, Claude Code
- Review period
- 7 Oct 2026 – 9 Oct 2026
- ✓AI code audit6 checks · 7 Oct 2026
- ✓Installed & run7 Oct 2026
- ✓Demo vs delivered7 Oct 2026
- ✓Final sign-off9 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 93/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 real credentials found. The demo password mechanism is secure (random generation + bcrypt storage). However, .env.example ships with DB_PASSWORD blank by default, and the demo password helper could theoretically leak if misconfigured. The SQL scripts contain bcrypt hashes only (safe). All API key placeholders are properly marked as examples. | 92 | Warning |
| Dependency vulnerabilities | All production dependencies are pinned to exact versions in both package.json and composer.json. Lockfiles are present (package-lock.json and composer.lock are referenced in the file tree). No known critical vulnerabilities detected in the declared versions. A few packages are slightly outdated but pose no immediate security risk. | 95 | Pass |
| Authorisation & access control | All mutating endpoints are properly guarded with authentication middleware and role/permission checks. Admin routes require authentication and appropriate roles. API endpoints use Sanctum token authentication with company scoping. Minor gaps: a few read endpoints lack explicit ownership validation when fetching records by ID, allowing potential cross-company data leakage if company scoping fails. | 95 | Warning |
| Database access rules | No SQL injection found. Query builders and Eloquent are used correctly throughout. One unscoped delete in ApiTokenController (line 47) operates on a scoped query so is safe in practice. Schema migrations are complete with foreign keys and cascades. Missing indexes on a few foreign key columns (warehouse_id, supplier_id in some tables) could cause N+1 or slow joins at scale. | 92 | Warning |
| Code structure & duplication | The codebase demonstrates solid architectural separation with domain-driven design, but several workflow classes exceed 300 lines and contain duplicated state-machine logic. Configuration values are mostly externalized, though some magic numbers appear in business logic. The structure is maintainable but could benefit from workflow abstraction and reducing duplication in approval/status handling. | 78 | Warning |
| Build reproducibility | The project is fully reproducible: all dependencies are pinned, Docker and XAMPP paths are documented, and the setup scripts work. Minor issues: HowToSetup.md section 3 references a PowerShell command for password generation that isn't shown, and the SQL Server Docker init script path in docker-compose.yml doesn't match the documented location. These don't block building but could confuse first-time users. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
No SQL injection found. Query builders and Eloquent are used correctly throughout. One unscoped delete in ApiTokenController (line 47) operates on a scoped query so is safe in practice. Schema migrations are complete with foreign keys and cascades. Missing indexes on a few foreign key columns (warehouse_id, supplier_id in some tables) could cause N+1 or slow joins at scale.
No real credentials found. The demo password mechanism is secure (random generation + bcrypt storage). However, .env.example ships with DB_PASSWORD blank by default, and the demo password helper could theoretically leak if misconfigured. The SQL scripts contain bcrypt hashes only (safe). All API key placeholders are properly marked as examples.
All mutating endpoints are properly guarded with authentication middleware and role/permission checks. Admin routes require authentication and appropriate roles. API endpoints use Sanctum token authentication with company scoping. Minor gaps: a few read endpoints lack explicit ownership validation when fetching records by ID, allowing potential cross-company data leakage if company scoping fails.
The codebase demonstrates solid architectural separation with domain-driven design, but several workflow classes exceed 300 lines and contain duplicated state-machine logic. Configuration values are mostly externalized, though some magic numbers appear in business logic. The structure is maintainable but could benefit from workflow abstraction and reducing duplication in approval/status handling.
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 7 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 7 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 9 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.