‹ Smart TreasuryQuality report QR-26-00048
Smart Treasury
Secure desktop wealth tracker using your own Google Sheet as database — banks, deposits, shares, business.
- Product ID
- B0408-33675
- Builder
- Uptechture Soft
- Version reviewed
- 1.0.0 · released 22 Oct 2026
- Stack
- Electron 44.9.0 · JavaScript (Node.js 20.18+) · Google Sheets (via REST API v4)
- Built with
- Claude Code
- Review period
- 20 Oct 2026 – 22 Oct 2026 · 1 round of changes
- ✓AI code audit6 checks · 19 Oct 2026
- ✓Installed & run21 Oct 2026
- ✓Demo vs delivered22 Oct 2026
- ✓Final sign-off22 Oct 2026
At a glance
- ✓Installed and run from the delivered code — 7 of 7 checks answered yes.
- ✓Live demo compared with the delivered code — 7 of 7 checks answered yes.
- ✓14 of 14 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 80/100.
- !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 | The codebase contains no hardcoded API keys, private keys, or credentials. All sensitive data (Google service account key, spreadsheet ID, master password) is entered by the user through the setup screen and stored encrypted locally. The .env.example files contain only feature flags and optional paths, no secrets. | 100 | Pass |
| Dependency vulnerabilities | package-lock.json is present and all dependencies are pinned. Electron 44.9.0 is 3 minor versions behind the latest 44.x (44.12.0 as of Jan 2025), and Chart.js 4.5.1 is behind 4.6.0. No known critical vulnerabilities found in the declared versions, but staying current reduces exposure to undisclosed issues. | 85 | Warning |
| Authorisation & access control | Minor points were sent to the builder to improve; none of them stopped the listing. | 45 | Fail |
| Database access rules | The app uses Google Sheets as the database with a REST API client that properly escapes values. No raw SQL concatenation or injection paths exist. The schema.sql is complete with foreign keys and CASCADE rules. Minor: foreign key columns lack explicit indexes (Google Sheets has no indexes, but the SQL schema should declare them for portability). | 95 | Pass |
| Code structure & duplication | The project has good module separation (main/renderer/test) and no god files, but several concerns reduce maintainability: password field UI is duplicated across auth screens, financial calculations are mixed with formatting logic, and some view files exceed 500 lines. Hard-coded strings and magic numbers appear in multiple places. | 72 | Warning |
| Build reproducibility | The project is well-structured with a complete package-lock.json, clear build scripts, and comprehensive setup documentation. All dependencies resolve correctly and build steps are documented. Minor issues: HowToSetup.md doesn't specify exact Node.js version (package.json requires >=20.18), and the Google service account setup process could be more explicit about JSON key format requirements. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
package-lock.json is present and all dependencies are pinned. Electron 44.9.0 is 3 minor versions behind the latest 44.x (44.12.0 as of Jan 2025), and Chart.js 4.5.1 is behind 4.6.0. No known critical vulnerabilities found in the declared versions, but staying current reduces exposure to undisclosed issues.
The project has good module separation (main/renderer/test) and no god files, but several concerns reduce maintainability: password field UI is duplicated across auth screens, financial calculations are mixed with formatting logic, and some view files exceed 500 lines. Hard-coded strings and magic numbers appear in multiple places.
Requirement list
What the builder agreed to deliver before uploading — 14 of 14 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
- Pinned dependencies without critical CVEs (nice)Met
- Documentation set (nice)Met
- Demo download or video 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 21 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 | N/A |
Stage 2 — Live demo compared with the delivered code
Completed 22 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 22 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.