‹ ERPQuality report QR-26-00080
ERP
Laravel HR, payroll & business ERP for Bangladeshi SMEs with biometric attendance and labour-law compliance
- Product ID
- B0561-99527
- Builder
- MD. SOHARAWARDY SHUVO
- Version reviewed
- 1.0.0 · released 28 Oct 2026
- Stack
- Laravel 12 · PHP 8.2+ · MySQL 5.7+ / MariaDB 10.3+
- Built with
- Claude Code
- Review period
- 24 Oct 2026 – 28 Oct 2026 · 2 rounds of changes
- ✓AI code audit6 checks · 23 Oct 2026
- ✓Installed & run28 Oct 2026
- ✓Demo vs delivered28 Oct 2026
- ✓Final sign-off28 Oct 2026
At a glance
- !Installed and run from the delivered code — 6 of 7 checks answered yes.
- ✓Live demo compared with the delivered code — 7 of 7 checks answered yes.
- !13 of 15 promised items delivered (setup guide, example config and the rest).
- !Security scored 60/100.
- !3 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 live API keys or production credentials were found. However, the seed data and documentation contain weak default passwords ([hidden]) that ship to buyers and could be exploited if not changed immediately after deployment. The .env.example file correctly uses placeholders. | 92 | Warning |
| Dependency vulnerabilities | Minor points were sent to the builder to improve; none of them stopped the listing. | 45 | Fail |
| Authorisation & access control | Minor points were sent to the builder to improve; none of them stopped the listing. | 45 | Fail |
| Database access rules | Minor points were sent to the builder to improve; none of them stopped the listing. | 42 | Fail |
| Code structure & duplication | The codebase has readable module boundaries but exhibits significant duplication in controllers (especially Admin/EmployeeController and EmployeeController), hard-coded configuration values scattered throughout, and some business logic leaking into views. Several controllers exceed 300 lines with mixed concerns. While not a critical failure, this increases maintenance burden and makes feature changes error-prone. | 68 | Warning |
| Build reproducibility | The project can be built on a clean machine but HowToSetup.md omits critical steps: it never instructs the user to copy .env.example to .env or generate APP_KEY, the Docker setup is incomplete (no volume mounts, no .env reference), and frontend asset compilation (npm install && npm run prod) is not documented. The database schema.sql and seed.sql are present but the setup doc does not explain when to import them. | 72 | Warning |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
The codebase has readable module boundaries but exhibits significant duplication in controllers (especially Admin/EmployeeController and EmployeeController), hard-coded configuration values scattered throughout, and some business logic leaking into views. Several controllers exceed 300 lines with mixed concerns. While not a critical failure, this increases maintenance burden and makes feature changes error-prone.
No live API keys or production credentials were found. However, the seed data and documentation contain weak default passwords ([hidden]) that ship to buyers and could be exploited if not changed immediately after deployment. The .env.example file correctly uses placeholders.
The project can be built on a clean machine but HowToSetup.md omits critical steps: it never instructs the user to copy .env.example to .env or generate APP_KEY, the Docker setup is incomplete (no volume mounts, no .env reference), and frontend asset compilation (npm install && npm run prod) is not documented. The database schema.sql and seed.sql are present but the setup doc does not explain when to import them.
Requirement list
What the builder agreed to deliver before uploading — 13 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 Partial
- 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
- .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 28 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 | N/A | |
| Branding and company details can be changed without code | No |
Stage 2 — Live demo compared with the delivered code
Completed 28 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 28 Oct 2026 with 3 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.