‹ Baki Khata: Digital Due-Book with SMS RemindersQuality report QR-26-00064
Baki Khata: Digital Due-Book with SMS Reminders
Digital due-book for shops selling on credit: ledgers, orders, SMS reminders, PDF statements, REST API.
- Product ID
- B0344-67728
- Builder
- Infymerce
- Version reviewed
- 1.0.0 · released 26 Oct 2026
- Stack
- Laravel 12 + Filament 4 · PHP 8.2+ · MySQL 8.0 / MariaDB 10.6+ (SQLite for testing)
- Built with
- Claude Code
- Review period
- 25 Oct 2026 – 26 Oct 2026
- ✓AI code audit6 checks · 25 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 — 6 of 8 checks answered yes.
- ✓Live demo compared with the delivered code — 7 of 7 checks answered yes.
- !14 of 15 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 88/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 | All sensitive values are properly externalized to environment variables. The .env.example file contains only placeholders (openssl commands, 'choose-a-strong-password'). Database credentials, admin passwords, and API keys are all loaded from environment variables with no hardcoded defaults. The codebase follows security best practices for credential management. | 100 | Pass |
| Dependency vulnerabilities | The project includes composer.json and composer.lock (435 KB) with Laravel 12, Filament 4, and other dependencies properly locked. No known critical vulnerabilities were identified in the declared versions. The lockfile is present and comprehensive, indicating good dependency management practices. | 85 | Warning |
| Authorisation & access control | All admin panel routes are guarded by Filament's auth middleware and scoped to owners via ScopedToOwner trait. API endpoints require Sanctum tokens and active user checks. Minor gaps: /api/v1/settings/translations/{locale} and /api/v1/settings/public lack authentication, allowing anyone to read app settings and translations. These are low-risk read-only endpoints but should document the public intent. | 92 | Warning |
| Database access rules | No SQL injection vulnerabilities detected—all raw SQL uses parameter binding correctly. However, multiple foreign key columns lack indexes (customer_id, user_id, order_id in various tables), which will cause performance issues at scale. The Transaction model's delete() method lacks user scoping, allowing cross-user deletion via client_uuid. Schema migrations are complete and can build from empty. | 72 | Warning |
| Code structure & duplication | The project has good separation of concerns with dedicated service classes, but exhibits moderate duplication in API controllers, form schemas, and table definitions. A few files exceed comfortable maintenance thresholds. No dead code detected, but some hard-coded values should move to configuration. | 78 | Warning |
| Build reproducibility | The project is fully reproducible from the archive. Composer dependencies resolve correctly, Docker setup is complete and coherent, and the manual setup steps work. Minor issues: HowToSetup.md doesn't specify the exact PHP extensions needed (listed in README but not setup doc), and the web installer path isn't mentioned in the Docker quickstart flow. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
The project includes composer.json and composer.lock (435 KB) with Laravel 12, Filament 4, and other dependencies properly locked. No known critical vulnerabilities were identified in the declared versions. The lockfile is present and comprehensive, indicating good dependency management practices.
The project has good separation of concerns with dedicated service classes, but exhibits moderate duplication in API controllers, form schemas, and table definitions. A few files exceed comfortable maintenance thresholds. No dead code detected, but some hard-coded values should move to configuration.
All admin panel routes are guarded by Filament's auth middleware and scoped to owners via ScopedToOwner trait. API endpoints require Sanctum tokens and active user checks. Minor gaps: /api/v1/settings/translations/{locale} and /api/v1/settings/public lack authentication, allowing anyone to read app settings and translations. These are low-risk read-only endpoints but should document the public intent.
No SQL injection vulnerabilities detected—all raw SQL uses parameter binding correctly. However, multiple foreign key columns lack indexes (customer_id, user_id, order_id in various tables), which will cause performance issues at scale. The Transaction model's delete() method lacks user scoping, allowing cross-user deletion via client_uuid. Schema migrations are complete and can build from empty.
Requirement list
What the builder agreed to deliver before uploading — 14 of 15 met.
- Complete source for every component Partial
- 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 | No | |
| 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 | No |
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 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.