‹ HR Manager: Employees, Attendance, Leave & PayrollQuality report QR-26-00065
HR Manager: Employees, Attendance, Leave & Payroll
Employee, attendance, leave, payroll and hiring system for small companies
- Product ID
- B0344-77482
- Builder
- Infymerce
- Version reviewed
- 1.0.0 · released 26 Oct 2026
- Stack
- Laravel 13.17 + Filament 5.10 · PHP 8.3+ · MySQL 8.0+ (SQLite for local development)
- Built with
- Claude Code
- Review period
- 24 Oct 2026 – 26 Oct 2026
- ✓AI code audit6 checks · 24 Oct 2026
- ✓Installed & run26 Oct 2026
- ✓Demo vs delivered26 Oct 2026
- ✓Final sign-off26 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 96/100 with no failing check.
- !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 | All sensitive configuration is properly externalized to environment variables. The .env.example file contains only placeholders and instructions. Database passwords, admin passwords, and API keys are all loaded from environment variables with appropriate validation. | 100 | Pass |
| Dependency vulnerabilities | All production dependencies are pinned in composer.lock and package-lock.json. No known critical vulnerabilities detected in Laravel 13.17, Filament 5.10, or other packages. A few dev dependencies could be updated but pose no security risk. | 95 | Pass |
| Authorisation & access control | All mutating endpoints are properly guarded with authentication and policies. Filament resources use comprehensive policies checking roles and reporting lines. Two minor gaps: the public careers page lacks rate limiting per IP (only per email), and the demo landing page at `/` is accessible without authentication when DEMO_MODE is off and careers are disabled. | 95 | Warning |
| Database access rules | No SQL injection risks found. Query builders and Eloquent are used correctly throughout. One unscoped delete in EmployeeService (line 113) operates on user data without a WHERE clause, though it's protected by policy checks. Several foreign key columns lack indexes (employee_id, leave_type_id, shift_id in multiple tables), which will hurt performance as data grows. | 92 | Warning |
| Code structure & duplication | The application has well-organized module boundaries with business logic properly isolated in Services. However, there is significant duplication between .agents/ and .claude/ skill directories (identical copies), and some configuration values are hard-coded in documentation rather than centralized. A few oversized files exist but are acceptable for their domain. | 78 | Warning |
| Build reproducibility | The project is fully reproducible via Docker Compose or manual setup. All dependencies resolve correctly, framework versions are consistent (Laravel 13, Filament 5, PHP 8.3+), and build artifacts are properly excluded. Minor issues: HowToSetup.md references a non-existent a project file file for manual setup, and the Docker entrypoint script location isn't documented. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
All mutating endpoints are properly guarded with authentication and policies. Filament resources use comprehensive policies checking roles and reporting lines. Two minor gaps: the public careers page lacks rate limiting per IP (only per email), and the demo landing page at `/` is accessible without authentication when DEMO_MODE is off and careers are disabled.
The application has well-organized module boundaries with business logic properly isolated in Services. However, there is significant duplication between .agents/ and .claude/ skill directories (identical copies), and some configuration values are hard-coded in documentation rather than centralized. A few oversized files exist but are acceptable for their domain.
No SQL injection risks found. Query builders and Eloquent are used correctly throughout. One unscoped delete in EmployeeService (line 113) operates on user data without a WHERE clause, though it's protected by policy checks. Several foreign key columns lack indexes (employee_id, leave_type_id, shift_id in multiple tables), which will hurt performance as data grows.
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 26 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 26 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 26 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.