‹ EasyTaskAIQuality report QR-26-00088

EasyTaskAI
AI-powered social media manager for creators, agencies and small businesses
- Product ID
- B0308-98564
- Builder
- Jehan Ahmed
- Version reviewed
- 1.5.0 · released 4 Nov 2026
- Stack
- Express 5.3 · Node.js 20+ · PostgreSQL 15+ (Supabase)
- Built with
- Lovable
- Review period
- 30 Oct 2026 – 4 Nov 2026
- ✓AI code audit6 checks · 30 Oct 2026
- ✓Installed & run3 Nov 2026
- ✓Demo vs delivered4 Nov 2026
- ✓Final sign-off4 Nov 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.
- !11 of 15 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 75/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 | Every secret-scan candidate is either a variable reference (process.env, cfg.supabaseAnonKey) or OAuth token handling at runtime, not a hardcoded credential. .env.example holds only blank placeholders, and the README states demo passwords are not shipped. Small deductions for items that could not be fully verified from the excerpts. | 92 | Pass |
| Dependency vulnerabilities | package.json pins all 10 production dependencies to exact versions and package-lock.json exists, so there are no wildcards, missing lockfiles, or known critical vulnerabilities that I can confirm. A few versions are unusually new, so I cannot verify them against advisories from the digest alone. The Node version requirement is inconsistent across package.json, docker-compose and the declared stack. | 82 | Pass |
| Authorisation & access control | Only a fraction of server.js (223 KB) was visible, so the route-by-route trace could not be completed. What is visible is encouraging: a requireAuth middleware, a resolveWorkspace membership check, owner-scoped service-role queries, and signature verification on the Paddle webhook. However, the service-role client bypasses RLS, so a single missed ownership check exposes data, and several public endpoints need confirmation. | 60 | Warning |
| Database access rules | The visible code uses supabase-js (parameterized) with a service-role client and relies on code-level owner scoping, with RLS as defense-in-depth. No injection path or unscoped delete is visible in the provided excerpts. Most of server.js (223 KB) and the 37 migrations were not shown, so scoping, foreign keys and indexes cannot be fully verified, and the service-role pattern adds risk. | 72 | Warning |
| Code structure & duplication | The lib/platforms, lib/video and worker split is sensible and each platform adapter follows one interface. However, server.js (223 KB) holds all /api routes, and a project file mixes theme, nav, auth and chrome concerns, which makes the codebase hard to navigate for a buyer extending it. | 72 | Warning |
| Build reproducibility | A clean machine can most likely restore and start the app: package.json pins exact versions, engines requires Node >=22, the README orders the steps database, config, then processes, and docker-compose is coherent. The declared stack (Node 20+) conflicts with the real requirement (Node 22+), and several referenced files were not shown. Those gaps stop this short of a clean pass. | 82 | Warning |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
The lib/platforms, lib/video and worker split is sensible and each platform adapter follows one interface. However, server.js (223 KB) holds all /api routes, and a project file mixes theme, nav, auth and chrome concerns, which makes the codebase hard to navigate for a buyer extending it.
The visible code uses supabase-js (parameterized) with a service-role client and relies on code-level owner scoping, with RLS as defense-in-depth. No injection path or unscoped delete is visible in the provided excerpts. Most of server.js (223 KB) and the 37 migrations were not shown, so scoping, foreign keys and indexes cannot be fully verified, and the service-role pattern adds risk.
A clean machine can most likely restore and start the app: package.json pins exact versions, engines requires Node >=22, the README orders the steps database, config, then processes, and docker-compose is coherent. The declared stack (Node 20+) conflicts with the real requirement (Node 22+), and several referenced files were not shown. Those gaps stop this short of a clean pass.
Only a fraction of server.js (223 KB) was visible, so the route-by-route trace could not be completed. What is visible is encouraging: a requireAuth middleware, a resolveWorkspace membership check, owner-scoped service-role queries, and signature verification on the Paddle webhook. However, the service-role client bypasses RLS, so a single missed ownership check exposes data, and several public endpoints need confirmation.
Requirement list
What the builder agreed to deliver before uploading — 11 of 15 met.
- Complete source for every component Met
- No real credentials in the archive Met
- Builds from a clean machine Partial
- Database script or migrations Met
- Authentication and roles on every mutating endpoint Partial
- Pinned dependencies without critical CVEs (nice)Partial
- Documentation set (nice)Met
- Working live demo Partial
- 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 3 Nov 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 Nov 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 Nov 2026 with 4 warnings shown publicly.
What this report covers — and what it doesn't
- It covers version 1.5.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-00088 | 1.5.0 | 4 Nov 2026 | 77 | Current |
| QR-26-00067 | 1.0.0 | 27 Oct 2026 | 92 | Replaced |
Vibe96 FZ-LLC, Dubai, UAE. This report describes the product at the time of review and is not a warranty.