‹ UPTECH Smart Shop Management (Inventory - POS - Invoice)Quality report QR-26-00070
UPTECH Smart Shop Management (Inventory - POS - Invoice)
Desktop POS, inventory and invoicing for retail and super shops with Google Sheets as the shared database
- Product ID
- B0408-84805
- Builder
- Uptechture Soft
- Version reviewed
- 1.0.0 · released 27 Oct 2026
- Stack
- Electron 45 + vanilla JavaScript (no framework) · JavaScript ES2020 · Google Sheets (via Apps Script) or local JSON cache
- Built with
- Claude Code
- Review period
- 22 Oct 2026 – 27 Oct 2026 · 2 rounds of changes
- ✓AI code audit6 checks · 22 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.
- !13 of 14 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 97/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 sensitive configuration is properly externalized. The .env.example files contain only placeholder comments with no actual values. Google Sheets credentials (Web App URL and API key) are entered through the UI and stored in local settings files, never committed to source. PIN hashes use salted [hidden] | 100 | Pass |
| Dependency vulnerabilities | The project has zero runtime dependencies (vanilla JS, no bundler). All three dev dependencies (electron, electron-builder, cross-env) are present in package-lock.json with pinned versions. Electron 45.0.0 is outdated (current stable is 33.x LTS or 34.x stable as of early 2025; 45.x does not exist yet—likely a typo for 25.x). electron-builder 26.15.3 has moderate advisories in its transitive logging chain (sprintf-js) that never run in production. No critical vulnerabilities found. | 85 | Warning |
| Authorisation & access control | Every IPC channel is checked against a role matrix in a project file before the handler runs. PINs are salted SHA-256 hashes. Session state lives in the main process only. All create/update/delete operations require authentication and appropriate roles. Minor: some read endpoints (products, customers, suppliers) lack per-record ownership checks, but the app is designed for shared shop data where all staff see all records. | 95 | Pass |
| Database access rules | The application uses Google Sheets as its database with a custom ORM (store.js) that never builds SQL strings. All destructive operations (delete, update) are scoped by ID or filtered predicates. The schema (schema.sql) defines all tables with primary keys, foreign keys, CHECK constraints, and indexes on foreign key columns. Minor: a few foreign key indexes could be composite for multi-column lookups. | 95 | Pass |
| Code structure & duplication | The codebase has good separation of concerns (main/renderer/shared) and no pervasive copy-paste, but several files exceed 500 lines and contain mixed responsibilities. a project file and docs are duplicated across root and Project/ folders. Some hard-coded values (timeouts, limits) should move to config. | 72 | Warning |
| Build reproducibility | The project is well-structured with consistent dependencies and clear build scripts. All package references resolve correctly, and the setup document covers the essential steps. Minor issues: Node.js version requirement (20.18+) is only in package.json engines field but not prominently stated in HowToSetup.md; the Google Sheets setup prerequisite is mentioned but could be clearer about when it's needed; no explicit mention of git requirement for cloning. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
The project has zero runtime dependencies (vanilla JS, no bundler). All three dev dependencies (electron, electron-builder, cross-env) are present in package-lock.json with pinned versions. Electron 45.0.0 is outdated (current stable is 33.x LTS or 34.x stable as of early 2025; 45.x does not exist yet—likely a typo for 25.x). electron-builder 26.15.3 has moderate advisories in its transitive logging chain (sprintf-js) that never run in production. No critical vulnerabilities found.
The codebase has good separation of concerns (main/renderer/shared) and no pervasive copy-paste, but several files exceed 500 lines and contain mixed responsibilities. a project file and docs are duplicated across root and Project/ folders. Some hard-coded values (timeouts, limits) should move to config.
Requirement list
What the builder agreed to deliver before uploading — 13 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 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 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
- Round 1: changes requested on 26 Oct 2026; the builder fixed them and uploaded again.
- 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.