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.3.0 · released 7 Oct 2026
Stack: ASP.NET Core 10 MVC · C# 13 / .NET 10 · SQL Server 2019
Built with: Claude Code
Review period: 7 Oct 2026 – 7 Oct 2026

Download PDF View the product

92out of 100 Passed with 3 warningsPass mark 75 and no failing check.

Scores

Security93

Code structure78

Docs & completeness100

Dependency health95

Build & deploy95

AI code audit6 checks · 7 Oct 2026
Installed & run7 Oct 2026
Demo vs delivered7 Oct 2026
Final sign-off7 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 93/100 with no failing check.
3 open warnings — explained in part 1.

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 found in the codebase. All connection strings and passwords in the source code are placeholders (CHANGE_ME_STRONG_PASSWORD_HERE, YOUR_SQL_SERVER). However, the seed.sql file creates demo accounts with a shared weak password that is printed to console and documented in user guides, which could be exploited if not changed before deployment.	95	Warning
Dependency vulnerabilities	The project uses .NET 10 with a lockfile (packages.lock.json) that pins all dependencies. All packages are current stable releases with no known critical vulnerabilities. The global.json enforces SDK 10.0.100+, which is the current .NET 10 release.	95	Pass
Authorisation & access control	All mutating endpoints require authentication. Admin routes enforce the SystemAdmin policy. Passwords use BCrypt. The main gaps are missing ownership checks on personal data reads (GET /api/me/boards, GET /api/me/notifications) where user A could read user B's data by changing the userId parameter, and the /api/boards/{id} GET endpoint lacks an explicit board-access check before returning the full aggregate.	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 to 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 architecture is well-organized with clear separation of concerns (Services, Repositories, Controllers, Views). However, there is notable duplication in JavaScript board modules, some large service files, and hard-coded values scattered across configuration. The codebase is navigable but would benefit from extracting repeated patterns and centralizing magic numbers.	78	Warning
Build reproducibility	The solution builds cleanly with .NET 10 SDK and SQL Server 2019+. All project references resolve, framework versions are consistent, and HowToSetup.md provides complete Windows/IIS and Docker instructions. Two minor issues: docker-compose.yml references a non-existent Dockerfile path, and the .env.example has a placeholder that doesn't match the documented pattern.	95	Pass

Open warnings

Problems that did not stop the listing. They stay on the product page until a later version fixes them.

Warning 1 Weak default passwords in documentation and examples; no real credentials found

No real credentials were found in the codebase. All connection strings and passwords in the source code are placeholders (CHANGE_ME_STRONG_PASSWORD_HERE, YOUR_SQL_SERVER). However, the seed.sql file creates demo accounts with a shared weak password that is printed to console and documented in user guides, which could be exploited if not changed before deployment.

Warning 2 Strong authentication and role guards; minor ownership gaps on personal data reads

All mutating endpoints require authentication. Admin routes enforce the SystemAdmin policy. Passwords use BCrypt. The main gaps are missing ownership checks on personal data reads (GET /api/me/boards, GET /api/me/notifications) where user A could read user B's data by changing the userId parameter, and the /api/boards/{id} GET endpoint lacks an explicit board-access check before returning the full aggregate.

Warning 3 Moderate code duplication and some oversized files; structure is sound but maintainability could improve

The architecture is well-organized with clear separation of concerns (Services, Repositories, Controllers, Views). However, there is notable duplication in JavaScript board modules, some large service files, and hard-coded values scattered across configuration. The codebase is navigable but would benefit from extracting repeated patterns and centralizing magic numbers.

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

Part 2

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 7 Oct 2026

A 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 7 Oct 2026

A 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 7 Oct 2026 with 3 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-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.