‹ FlowBoardQuality report QR-26-00005
This report has been replaced — a newer version of FlowBoard was reviewed. See the current report (QR-26-00031) →
FlowBoard
Project management system like Trello
- Product ID
- B0001-89077
- Builder
- X1980 Group
- Version reviewed
- 1.0.0 · released 4 Oct 2026
- Stack
- C# · C# · MSSQL
- Built with
- Claude Code
- Review period
- 4 Oct 2026 – 4 Oct 2026
- ✓AI code audit6 checks · 4 Oct 2026
- ✓Installed & run4 Oct 2026
- ✓Demo vs delivered4 Oct 2026
- ✓Final sign-off4 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 92/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 | No real credentials were committed. However, documentation files contain weak placeholder passwords like 'CHANGE_ME_STRONG_PASSWORD_HERE' that could be deployed unchanged if a buyer skips the setup instructions. The demo seed data creates accounts with a shared password (printed during setup). All placeholders are clearly marked but should be validated at runtime. | 92 | Warning |
| Dependency vulnerabilities | The project uses .NET 10 with a packages.lock.json lockfile that pins all dependencies to exact versions. All packages are current stable releases from Microsoft and reputable publishers. No known critical vulnerabilities detected in the dependency tree. | 95 | Pass |
| Authorisation & access control | All mutating endpoints require authentication with proper role checks for admin routes. Passwords use bcrypt. The fallback authorization policy requires authenticated users by default. Minor gaps: some read endpoints (workspace members, board files, audit log user filter) lack explicit ownership checks, allowing users to enumerate data by changing IDs. | 92 | Warning |
| Database access rules | All SQL is hand-written ADO.NET with parameters—no concatenation or injection paths found. Delete and update statements are properly scoped to user/workspace/board. The schema script creates every table with foreign keys and sensible cascades. Three foreign key columns lack indexes (Cards.MirrorCardId, CardMembers.UserId, CardVotes.UserId), which will cause table scans on common queries. | 92 | Warning |
| Code structure & duplication | The project demonstrates good separation of concerns with clear module boundaries (Controllers, Services, Repositories, Infrastructure). Business logic is properly isolated in the Application/Services layer. However, there is some duplication in validation logic, magic numbers scattered across files, and a few oversized service classes that could benefit from further decomposition. | 82 | Pass |
| Build reproducibility | The .NET solution builds cleanly with consistent SDK/framework versions (10.0.100/.NET 10). Database scripts are present and complete. The main setup document (HowToSetup.md) provides clear Windows/IIS and Docker paths. Minor issues: docker-compose.yml references a project filee but the actual .env location is ambiguous, and the SQL Server container initialization in docker-compose.yml lacks explicit schema/seed execution steps that HowToSetup.md describes. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
No real credentials were committed. However, documentation files contain weak placeholder passwords like 'CHANGE_ME_STRONG_PASSWORD_HERE' that could be deployed unchanged if a buyer skips the setup instructions. The demo seed data creates accounts with a shared password (printed during setup). All placeholders are clearly marked but should be validated at runtime.
All mutating endpoints require authentication with proper role checks for admin routes. Passwords use bcrypt. The fallback authorization policy requires authenticated users by default. Minor gaps: some read endpoints (workspace members, board files, audit log user filter) lack explicit ownership checks, allowing users to enumerate data by changing IDs.
All SQL is hand-written ADO.NET with parameters—no concatenation or injection paths found. Delete and update statements are properly scoped to user/workspace/board. The schema script creates every table with foreign keys and sensible cascades. Three foreign key columns lack indexes (Cards.MirrorCardId, CardMembers.UserId, CardVotes.UserId), which will cause table scans on common queries.
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
- 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 4 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 4 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 4 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.
Report history
| Report | Version | Date | Score | Status |
|---|---|---|---|---|
| QR-26-00031 | 1.3.0 | 7 Oct 2026 | 92 | Current |
| QR-26-00024 | 1.2.0 | 7 Oct 2026 | 0 | Replaced |
| QR-26-00005 | 1.0.0 | 4 Oct 2026 | 91 | Replaced |
Vibe96 FZ-LLC, Dubai, UAE. This report describes the product at the time of review and is not a warranty.