‹ TaskOQuality report QR-26-00058
TaskO
Self-hosted Kanban board system with timeline, calendar and automation for single-organisation teams
- Product ID
- B0001-89077
- Builder
- Ibrahim Abdurahman
- Version reviewed
- 1.4.0 · released 23 Oct 2026
- Stack
- ASP.NET Core 10 MVC · C# 13 / .NET 10 · SQL Server 2019
- Built with
- Claude Code
- Review period
- 23 Oct 2026 – 23 Oct 2026
- ✓AI code audit6 checks · 23 Oct 2026
- ✓Installed & run23 Oct 2026
- ✓Demo vs delivered23 Oct 2026
- ✓Final sign-off23 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 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. All connection strings and passwords in code are placeholders ([hidden], [hidden]). However, the tour demo includes a hardcoded TOTP secret for demonstration purposes, and documentation examples use weak placeholder patterns that could be mistaken for real values. | 92 | Warning |
| Dependency vulnerabilities | The project uses .NET 10 with a packages.lock.json lockfile. All NuGet packages are pinned to specific versions with no known critical vulnerabilities. A few packages are slightly behind latest stable releases but pose no security risk. | 95 | Pass |
| Authorisation & access control | All mutating endpoints require authentication and admin routes check SystemAdmin role. Passwords use BCrypt. The fallback authorization policy enforces sign-in globally. Two personal-data read endpoints (GET /api/me/notifications, GET /api/me/activity) lack explicit ownership checks beyond the signed-in user context, allowing enumeration of notification/activity IDs if an attacker can guess them. Board and workspace access is properly gated through AccessService. | 92 | Warning |
| Database access rules | All SQL is hand-written ADO.NET with parameters—no string concatenation or injection paths. DELETE and UPDATE statements correctly scope by user/board/workspace. The schema creates cleanly with foreign keys, but several FK columns lack indexes (performance risk under load) and cascade rules are absent (orphan risk on manual deletes). | 92 | Pass |
| Code structure & duplication | The project has good separation of concerns with clear layers (Controllers → Services → Repositories), but several files exceed 500 lines and contain duplicated logic. Board-related services are split well, but some utility code is repeated across JavaScript modules. Configuration values are mostly externalized, though a few hard-coded strings remain in non-config files. | 78 | Warning |
| 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 steps for local and IIS deployment. Docker setup has minor issues: the .env.example references a non-existent create-app-login.sql script, and docker-compose.yml uses an outdated image tag that doesn't match the current .NET version. | 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. All connection strings and passwords in code are placeholders ([hidden], [hidden]). However, the tour demo includes a hardcoded TOTP secret for demonstration purposes, and documentation examples use weak placeholder patterns that could be mistaken for real values.
The project has good separation of concerns with clear layers (Controllers → Services → Repositories), but several files exceed 500 lines and contain duplicated logic. Board-related services are split well, but some utility code is repeated across JavaScript modules. Configuration values are mostly externalized, though a few hard-coded strings remain in non-config files.
All mutating endpoints require authentication and admin routes check SystemAdmin role. Passwords use BCrypt. The fallback authorization policy enforces sign-in globally. Two personal-data read endpoints (GET /api/me/notifications, GET /api/me/activity) lack explicit ownership checks beyond the signed-in user context, allowing enumeration of notification/activity IDs if an attacker can guess them. Board and workspace access is properly gated through AccessService.
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 Partial
- 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 23 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 23 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 23 Oct 2026 with 3 warnings shown publicly.
What this report covers — and what it doesn't
- It covers version 1.4.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-00058 | 1.4.0 | 23 Oct 2026 | 91 | Current |
| QR-26-00031 | 1.3.0 | 7 Oct 2026 | 92 | Replaced |
| 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.