‹ EasyTaskAIQuality report QR-26-00067
EasyTaskAI
AI-powered social media manager for creators, agencies and small businesses
- Product ID
- B0308-98564
- Builder
- Jehan Ahmed
- Version reviewed
- 1.0.0 · released 27 Oct 2026
- Stack
- Express 5.3 · Node.js 20+ · PostgreSQL 15+ (Supabase)
- Built with
- Lovable
- Review period
- 23 Oct 2026 – 27 Oct 2026
- ✓AI code audit6 checks · 23 Oct 2026
- ✓Installed & run27 Oct 2026
- ✓Demo vs delivered27 Oct 2026
- ✓Final sign-off27 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 95/100 with no failing check.
- !2 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 API keys, tokens, and credentials are properly externalized to environment variables via .env (which is gitignored). The codebase contains only placeholder references and example documentation. Secret scanning regex hits are all legitimate code patterns (e.g., 'access_token' field names in OAuth flows, 'apikey' headers reading from config). | 100 | Pass |
| Dependency vulnerabilities | package.json declares 8 production dependencies with semantic versioning ranges (^). package-lock.json is present and pins exact versions. No known critical vulnerabilities found in the declared versions. All packages are actively maintained. Minor: some dependencies could be updated to latest (e.g., @supabase/supabase-js 2.118.0 → 2.47+, express 5.3.0 is pre-release), but none pose security risk. | 95 | Pass |
| Authorisation & access control | All mutating and admin endpoints require authentication and proper role checks. Workspace isolation is enforced via owner-scoped queries. Minor gaps: /api/posts/:id and /api/library/:id lack explicit ownership checks before returning data, relying solely on RLS. /api/demo-login has no rate limiting beyond the global 120/min API limiter. | 92 | Warning |
| Database access rules | All queries use parameterized statements or the Supabase client's safe methods—no SQL injection paths found. Delete and update operations are properly scoped to workspace/user ownership. Row Level Security policies are defined in migrations as defense-in-depth. The schema is complete and can be created from empty (migration-all.sql). Minor issue: several foreign key columns lack indexes, which will cause performance degradation as data grows. | 92 | Pass |
| Code structure & duplication | server.js is 123 KB with mixed concerns (auth, API routes, business logic). Platform adapters show copy-paste patterns for OAuth token exchange. Frontend views contain duplicated API call patterns and error handling. No dead code detected, but refactoring would improve maintainability. | 72 | Warning |
| Build reproducibility | All dependencies resolve, no conflicting versions, and the setup documents provide clear steps. Minor issues: SETUP-WINDOWS.md and HowToSetup.md are redundant; the main README references SETUP-WINDOWS.md but buyers may miss the more detailed a project file; migration execution order could be clearer for first-time operators. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
All mutating and admin endpoints require authentication and proper role checks. Workspace isolation is enforced via owner-scoped queries. Minor gaps: /api/posts/:id and /api/library/:id lack explicit ownership checks before returning data, relying solely on RLS. /api/demo-login has no rate limiting beyond the global 120/min API limiter.
server.js is 123 KB with mixed concerns (auth, API routes, business logic). Platform adapters show copy-paste patterns for OAuth token exchange. Frontend views contain duplicated API call patterns and error handling. No dead code detected, but refactoring would improve maintainability.
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
- .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 27 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 27 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 27 Oct 2026 with 2 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.
Vibe96 FZ-LLC, Dubai, UAE. This report describes the product at the time of review and is not a warranty.