TallySwift — quality report QR-26-00139 | Vibe96

‹ TallySwiftQuality report QR-26-00139

TallySwift
Vibe96 quality report

TallySwift

Self-hosted invoicing and payment tracking with Admin and User dashboards.

Product ID
B0555-62410
Builder
MST RATNA BEGUM
Version reviewed
1.0.0 · released 16 Nov 2026
Stack
Express 4.21.2 with vanilla JS front end and Tailwind CSS 3.4 · JavaScript (Node.js 22.16.x) and SQL · SQLite via better-sqlite3 11.8.1 (embedded, no separate server)
Built with
Claude Code
Review period
5 Nov 2026 – 16 Nov 2026 · 3 rounds of changes
73out of 100 Listed after a manual reviewPass mark 75 and no failing check.

Scores

Security86
Code structure62
Docs & completeness69
Dependency health62
Build & deploy40
  1. AI code audit6 checks · 5 Nov 2026
  2. Installed & run16 Nov 2026
  3. Demo vs delivered16 Nov 2026
  4. Final sign-off16 Nov 2026

At a glance

  • Installed and run from the delivered code — 5 of 8 checks answered yes.
  • Live demo compared with the delivered code — 7 of 7 checks answered yes.
  • 18 of 26 promised items delivered (setup guide, example config and the rest).
  • Security scored 86/100.
  • 3 open warnings — explained in part 1.
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.

CheckWhat we foundScoreResult
Secrets & credentialsThe regex hits are a placeholder in .env.example and code that reads SESSION_SECRET from the environment. No API keys, private keys, SMTP passwords or database credentials with real values are present in the shown files. Production startup rejects the placeholder and secrets under 32 characters, which limits the risk of a weak default shipping.96Pass
Dependency vulnerabilitiesAll dependencies in package.json are exactly pinned with no wildcards, which is good. However, the README admits the package-lock.json is a stub that was never generated by a real install, so the deployed versions are not reproducible or verifiable. Some pinned versions (express 4.21.2, better-sqlite3 11.8.1, pdfkit 0.16.0) are older than current releases and may have moderate advisories; none is a confirmed critical vulnerability.62Warning
Authorisation & access controlEvery clients, invoices, payments and analytics route sits behind requireAuth, and queries filter by the session user ID, so changing an id does not expose another user's records. Passwords are bcrypt-hashed and login rate-limited. Remaining gaps are minor: one payments query lacks a user filter on a join, and the status route body was not fully visible.90Pass
Database access rulesAll visible SQL uses prepared statements with bound parameters, and every read, update and delete on user data is scoped by user_id. The schema file was not provided in the excerpts, so foreign keys, indexes and cascade rules could not be verified. CLAUDE.md says migrate.js applies a root a project file, but the file lives at a project file, so creating the DB from empty may fail.72Warning
Code structure & duplicationThe backend is split into sensible modules (routes, services, db, middleware), which is a good boundary. However, many route and UI files are written as dense single-line blocks, and the frontend app.js is a single minified-style file that mixes views, API calls and modal logic, making the code hard to maintain and review.62Warning
Build reproducibilityMinor points were sent to the builder to improve; none of them stopped the listing.40Fail

Open warnings

Problems that did not stop the listing. They stay on the product page until a later version fixes them.

Warning 1 Lockfile is a stub; versions pinned but several have known moderate advisories and no audit evidence

All dependencies in package.json are exactly pinned with no wildcards, which is good. However, the README admits the package-lock.json is a stub that was never generated by a real install, so the deployed versions are not reproducible or verifiable. Some pinned versions (express 4.21.2, better-sqlite3 11.8.1, pdfkit 0.16.0) are older than current releases and may have moderate advisories; none is a confirmed critical vulnerability.

Warning 2 Business logic and routing are minified into one-line files; several modules are hard to navigate and duplicate logic

The backend is split into sensible modules (routes, services, db, middleware), which is a good boundary. However, many route and UI files are written as dense single-line blocks, and the frontend app.js is a single minified-style file that mixes views, API calls and modal logic, making the code hard to maintain and review.

Warning 3 Queries are parameterised and user-scoped, but schema was not visible and migrate path looks inconsistent

All visible SQL uses prepared statements with bound parameters, and every read, update and delete on user data is scoped by user_id. The schema file was not provided in the excerpts, so foreign keys, indexes and cascade rules could not be verified. CLAUDE.md says migrate.js applies a root a project file, but the file lives at a project file, so creating the DB from empty may fail.

Requirement list

What the builder agreed to deliver before uploading — 18 of 26 met.

  • Complete source for the whole app Partial
  • Pinned dependencies with lockfile Partial
  • SQLite schema creates from empty Partial
  • No real credentials: config files may be present but must contain placeholders or local defaults only Met
  • Authentication and role checks on every write route Met
  • Parameterised SQL and scoped deletes Met
  • HowToSetup.md with VPS and Docker paths Partial
  • Reachable live demo with sample data Partial
  • Verify the five datasheet features exist in code Met
  • Seed data for demo (nice)Missing
  • CLAUDE.md for AI coding tools (nice)Met
  • Docker compose for self-hosting (nice)Met
  • CHANGELOG starting at 1.0.0 (nice)Partial
  • Keep the app modular (optional)Met
  • README.md Met
  • HowToSetup.md Met
  • Node.js a project filee Met
  • Node.js a project file Met
  • Node.js a project file Met
  • a project file Met
  • a project file (nice)Missing
  • CLAUDE.md (nice)Met
  • CHANGELOG.md (nice)Met
  • docker-compose.yml (nice)Met
  • LICENSE-NOTE.md (nice)Met
  • a project file (optional)Met
Part 2

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 16 Nov 2026

A reviewer installed the product on a clean machine, following only the guide that ships with it.

QuestionAnswerReviewer's note
Packages restored without errorsYes
Solution builds cleanYes
Database created from the shipped script or migrationsYes
First sign-in works with the documented stepsYes
Setup guide is accurate and completeNo
Every module in the feature list opens and worksNo
No real secrets in the archiveYes
Branding and company details can be changed without codeNo

Stage 2 — Live demo compared with the delivered code

Completed 16 Nov 2026

A second reviewer checked that what the listing and demo show is what the buyer receives.

QuestionAnswerReviewer's note
Demo URL is reachableYes
Demo credentials workYes
Demo runs the same version as the archiveYes
All five differentiators are visible in the demoYes
Screenshots match the demoYes
Nothing in the demo is missing from the codeYes
Datasheet claims are accurateYes

Changes asked for during review

  • None — approved on the first round.
  • Sign-off: approved for sale on 16 Nov 2026 with 3 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.