‹ TradeVault — Crypto & Trading Portfolio TrackerQuality report QR-26-00110
TradeVault — Crypto & Trading Portfolio Tracker
Crypto and stock portfolio tracker with trade journal, alerts and risk analytics for retail investors.
- Product ID
- B0308-18324
- Builder
- Jehan Ahmed
- Version reviewed
- 1.0.0 · released 10 Nov 2026
- Stack
- React 18.3 + Vite 6.4 (Tailwind, Recharts) · TypeScript 5.9 (web) + JavaScript (Node server) · Supabase (PostgreSQL); no minimum version stated in code
- Built with
- Claude Code
- Review period
- 6 Nov 2026 – 10 Nov 2026 · 1 round of changes
- ✓AI code audit6 checks · 6 Nov 2026
- ✓Installed & run10 Nov 2026
- ✓Demo vs delivered10 Nov 2026
- ✓Final sign-off10 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.
- !17 of 24 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 84/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 | No API keys, private keys, service-role keys or connection strings were found; the other regex hits are code reading env vars or JWT header parsing. A shared demo account password is hardcoded in the frontend bundle and docs. The README says this is intentional and the account is RLS-scoped with fictional data, but it is still a real login credential for a live Supabase project that ships to buyers. | 80 | Warning |
| Dependency vulnerabilities | Both Web App and server have package.json with exact pins (no caret/wildcard ranges) and a package-lock.json, which is good practice. Some declared versions (nodemailer 10.3.1, vitest 4.1.12, vite 6.4.5, @supabase/supabase-js 2.119.0) could not be verified against known releases, and the README's '0 vulnerabilities' claim is self-reported. No known critical vulnerability is identifiable from the manifests. | 82 | Pass |
| Authorisation & access control | Every /api route sits behind requireAuth and requireDb, and user ids always come from the verified token. Most id lookups go through fetchOwned and writes filter by user_id. A few child-resource reads and updates skip parent ownership validation, but they only return the caller's own rows, so exposure is low. | 88 | Pass |
| Database access rules | All database access goes through the Supabase query builder with no string-built SQL, and every delete is scoped by id and user_id. Weaknesses are that updates filter only by id after an ownership pre-check, trade updates pass body fields through without validation, several list endpoints are capped at 500 rows, and schema.sql was not provided for review. | 84 | Warning |
| Code structure & duplication | The server is split into one route module per resource with shared helpers, and the web app separates lib, store, pages and components. Duplication is limited to repeated ownership-check and patch-building patterns, and some values such as rate limits and the demo password are hard-coded. | 84 | Pass |
| Build reproducibility | Manifests are coherent: exact-pinned dependencies, lockfiles in both packages, and Node >=18 declared. The demo bundle is served from a Vite build, and no build output or vendored folders appear in the tree. I could not read HowToSetup.md, schema.sql or the server env block, so setup order and prerequisites are unverified, and a few small gaps remain. | 84 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
No API keys, private keys, service-role keys or connection strings were found; the other regex hits are code reading env vars or JWT header parsing. A shared demo account password is hardcoded in the frontend bundle and docs. The README says this is intentional and the account is RLS-scoped with fictional data, but it is still a real login credential for a live Supabase project that ships to buyers.
All database access goes through the Supabase query builder with no string-built SQL, and every delete is scoped by id and user_id. Weaknesses are that updates filter only by id after an ownership pre-check, trade updates pass body fields through without validation, several list endpoints are capped at 500 rows, and schema.sql was not provided for review.
Requirement list
What the builder agreed to deliver before uploading — 17 of 24 met.
- Complete source for every part Partial
- No real credentials Partial
- Single example env file Partial
- Database schema creates from empty Met
- RLS and role checks on every write path Partial
- Pinned lockfile and no critical CVEs Met
- HowToSetup.md with two targets Partial
- Reachable demo with sample data Partial
- README.md with features and screenshots Met
- CLAUDE.md for AI coding tools (nice)Met
- CHANGELOG.md starting at 1.0.0 (nice)Met
- Seed data file (nice)Met
- Automated tests (nice)Partial
- Documentation folder (optional)Met
- README.md Met
- HowToSetup.md Met
- Web a project filee Met
- Web a project file Met
- a project file Met
- CLAUDE.md (nice)Met
- CHANGELOG.md (nice)Met
- a project file (nice)Met
- LICENSE-NOTE.md (nice)Met
- docs/ (optional)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 10 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 10 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 10 Nov 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.