‹ MailFlow AI Campaign PlatformQuality report QR-26-00042
MailFlow AI Campaign Platform
AI-personalised lead-generation email platform with drag-and-drop flow builder for B2B sales teams
- Product ID
- B0004-49915
- Builder
- Ibrahim Abdurahman
- Version reviewed
- 1.3.0 · released 19 Oct 2026
- Stack
- ASP.NET Core 10 · C# 10 · SQL Server 2019
- Built with
- Claude Code
- Review period
- 14 Oct 2026 – 19 Oct 2026
- ✓AI code audit6 checks · 14 Oct 2026
- ✓Installed & run19 Oct 2026
- ✓Demo vs delivered19 Oct 2026
- ✓Final sign-off19 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.
- !14 of 15 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 87/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 secrets are placeholders or environment variable references. The only issue is appsettings.json ships with Auth:AdminPassword empty, which creates the first admin with no password if not overridden. This is a weak default for local development but documented in HowToSetup.md and .env.example requires it. | 95 | Warning |
| Dependency vulnerabilities | The .NET project has no packages.lock.json, so dependency versions float within the ranges in MailFlow.csproj. All packages are current stable releases with no known critical vulnerabilities. Docker base images use floating tags (10.0, 2022-CU15) which is acceptable for auto-patching but means builds are not reproducible. | 95 | Pass |
| Authorisation & access control | Every mutating endpoint and page requires authentication via cookie auth with proper password hashing ([hidden]). All API routes check for X-MailFlow-Request header. Public tracking/unsubscribe routes are correctly anonymous. Minor issue: contact details and flow builder pages don't verify the requested contact/flow belongs to the signed-in user's workspace, allowing cross-tenant reads in a multi-tenant deployment (currently single-workspace by design | 95 | Warning |
| Database access rules | The schema deliberately omits foreign keys (documented choice), but lacks indexes on most foreign-key columns (ContactId, FlowId, TemplateId, etc.), creating N+1 query risks. One DELETE in FlowEngine.cs (line 394) removes all enrollments for a contact without scoping to the current flow, which could affect other flows. No SQL injection found; EF Core parameterizes everything. | 72 | Warning |
| Code structure & duplication | MailFlow has clear separation of concerns (Pages, Services, Engine, Endpoints) and no pervasive god files. However, there is notable duplication in validation logic, email composition, and flow node handling. A few service files exceed 400 lines and could benefit from further decomposition. Hard-coded values are mostly confined to configuration files, but some magic strings appear in multiple places. | 78 | Warning |
| Build reproducibility | The project builds cleanly with .NET 10 SDK and SQL Server 2019+. All references resolve, Docker setup is complete, and the main setup document covers all steps. Minor issues: HowToSetup.md doesn't specify the exact .NET SDK version (10.0.1xx from global.json), and the sqlcmd prerequisite for database creation isn't explicitly listed in the prerequisites section. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
All secrets are placeholders or environment variable references. The only issue is appsettings.json ships with Auth:AdminPassword empty, which creates the first admin with no password if not overridden. This is a weak default for local development but documented in HowToSetup.md and .env.example requires it.
Every mutating endpoint and page requires authentication via cookie auth with proper password hashing ([hidden]). All API routes check for X-MailFlow-Request header. Public tracking/unsubscribe routes are correctly anonymous. Minor issue: contact details and flow builder pages don't verify the requested contact/flow belongs to the signed-in user's workspace, allowing cross-tenant reads in a multi-tenant deployment (currently single-workspace by design
MailFlow has clear separation of concerns (Pages, Services, Engine, Endpoints) and no pervasive god files. However, there is notable duplication in validation logic, email composition, and flow node handling. A few service files exceed 400 lines and could benefit from further decomposition. Hard-coded values are mostly confined to configuration files, but some magic strings appear in multiple places.
The schema deliberately omits foreign keys (documented choice), but lacks indexes on most foreign-key columns (ContactId, FlowId, TemplateId, etc.), creating N+1 query risks. One DELETE in FlowEngine.cs (line 394) removes all enrollments for a contact without scoping to the current flow, which could affect other flows. No SQL injection found; EF Core parameterizes everything.
Requirement list
What the builder agreed to deliver before uploading — 14 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)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
- appsettings.example.json 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 19 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 19 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 19 Oct 2026 with 4 warnings shown publicly.
What this report covers — and what it doesn't
- It covers version 1.3.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.
Report history
| Report | Version | Date | Score | Status |
|---|---|---|---|---|
| QR-26-00042 | 1.3.0 | 19 Oct 2026 | 88 | Current |
| QR-26-00035 | 1.0.0 | 12 Oct 2026 | 85 | Replaced |
Vibe96 FZ-LLC, Dubai, UAE. This report describes the product at the time of review and is not a warranty.