LoyalBite — quality report QR-26-00074 | Vibe96

‹ LoyalBiteQuality report QR-26-00074

LoyalBite
Vibe96 quality report

LoyalBite

Multi-brand restaurant loyalty platform with POS-initiated transactions and mobile customer app

Product ID
B0003-72659
Builder
Max code
Version reviewed
1.3.0 · released 27 Oct 2026
Stack
ASP.NET Core 10 MVC + EF Core 10 · C# 12 (.NET 10) · SQL Server 2019
Built with
Claude Code
Review period
27 Oct 2026 – 27 Oct 2026
85out of 100 Passed with 3 warningsPass mark 75 and no failing check.

Scores

Security88
Code structure84
Docs & completeness94
Dependency health78
Build & deploy80
  1. AI code audit6 checks · 27 Oct 2026
  2. Installed & run27 Oct 2026
  3. Demo vs delivered27 Oct 2026
  4. 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.
  • 16 of 17 promised items delivered (setup guide, example config and the rest).
  • Security scored 88/100 with no failing check.
  • 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 & credentialsEvery regex candidate in the digest is a property name, an environment-variable reference, or a visibly fake test value. appsettings.json ships empty secrets and the app refuses to start without them. The only residual concern is a hardcoded fallback admin email and an unenforced placeholder check for .env values.95Pass
Dependency vulnerabilitiesLockfiles are present for the server (packages.lock.json), the tests and the Flutter POS app (pubspec.lock). The digest does not include LoyalBite.csproj or the lockfile contents, so installed versions could not be checked against advisories. The Docker base image is pinned by digest, which is good, but a customer-app pubspec.lock was not visible and Flutter pubspec constraints could not be checked.78Warning
Authorisation & access controlIn the files provided, authorization is sound: AccountController uses [Authorize] with anonymous login only, rate limiting and lockout. AuditController and NotificationsController are restricted to SuperAdmin, and the branding API is a deliberately public read-only endpoint. Most controllers (admin and customer API) were not shown, so ownership checks on id lookups and role checks on mutating routes are unverified. The score is capped for that gap, not for a demonstrated hole.82Warning
Database access rulesThe visible evidence shows EF Core LINQ, filters built with parameters, and a documented schema with foreign keys, indexes and sensible delete rules. The two raw-SQL exceptions (EarnOperation dedupe insert, backup/restore) are described as parameterized or model-derived, but their code was not in the digest, so they could not be verified. No injection path or unscoped destructive statement was found in the shown files.88Pass
Code structure & duplicationThe project is split into clear areas (Controllers, API, Services per domain, Pos operations, Startup, Middleware), and the digest shows no god files. The main weaknesses are small duplicated blocks in the admin controllers and a few hard-coded paging and rate-limit values that should live in configuration.84Pass
Build reproducibilityThe compose file is coherent, pins the SQL image by digest, and the .env.example placeholders are blocked by required-variable checks. The schema, upgrade scripts and a lockfile exist. HowToSetup.md, the csproj, Dockerfile and CI workflow were not in the excerpts, so the SDK version, prerequisites and step order could not be confirmed.80Warning

Open warnings

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

Warning 1 Lockfiles exist, but their contents were not provided, so no dependency can be confirmed free of known CVEs

Lockfiles are present for the server (packages.lock.json), the tests and the Flutter POS app (pubspec.lock). The digest does not include LoyalBite.csproj or the lockfile contents, so installed versions could not be checked against advisories. The Docker base image is pinned by digest, which is good, but a customer-app pubspec.lock was not visible and Flutter pubspec constraints could not be checked.

Warning 2 Build looks reproducible, but key manifests and HowToSetup.md could not be verified from the digest

The compose file is coherent, pins the SQL image by digest, and the .env.example placeholders are blocked by required-variable checks. The schema, upgrade scripts and a lockfile exist. HowToSetup.md, the csproj, Dockerfile and CI workflow were not in the excerpts, so the SDK version, prerequisites and step order could not be confirmed.

Warning 3 Visible routes are properly guarded; most controllers and API ownership checks could not be verified from the digest

In the files provided, authorization is sound: AccountController uses [Authorize] with anonymous login only, rate limiting and lockout. AuditController and NotificationsController are restricted to SuperAdmin, and the branding API is a deliberately public read-only endpoint. Most controllers (admin and customer API) were not shown, so ownership checks on id lookups and role checks on mutating routes are unverified. The score is capped for that gap, not for a demonstrated hole.

Requirement list

What the builder agreed to deliver before uploading — 16 of 17 met.

  • Complete source for every component Met
  • No real credentials in the archive Met
  • Builds from a clean machine Partial
  • 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
  • Mobile app buildable and pointed at a configurable API Met
  • README.md Met
  • HowToSetup.md Met
  • CLAUDE.md (or AGENTS.md) (nice)Met
  • CHANGELOG.md (nice)Met
  • appsettings.example.json Met
  • a project file Met
  • a project file (nice)Met
  • a project file 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 27 Oct 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 completeYes
Every module in the feature list opens and worksYes
No real secrets in the archiveYes
Branding and company details can be changed without codeYes

Stage 2 — Live demo compared with the delivered code

Completed 27 Oct 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 27 Oct 2026 with 3 warnings shown publicly.

What this report covers — and what it doesn't

  • It covers version 1.3.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.

Report history

ReportVersionDateScoreStatus
QR-26-000741.3.027 Oct 202685Current
QR-26-000161.0.06 Oct 202686Replaced

Vibe96 FZ-LLC, Dubai, UAE. This report describes the product at the time of review and is not a warranty.