Sitepulse — quality report QR-26-00144 | Vibe96

‹ SitepulseQuality report QR-26-00144

Sitepulse
Vibe96 quality report

Sitepulse

Self-hosted website analytics with live view, visitor profiles and chat, for teams on IIS or Docker with SQL Server.

Product ID
B0006-25310
Builder
Build Nest
Version reviewed
1.0.0 · released 17 Nov 2026
Stack
ASP.NET Core 10 MVC with Entity Framework Core 10, Razor views and Tailwind CSS 4 · C# / .NET 10 (ASP.NET Core 10 MVC) · Microsoft SQL Server 2016 SP1 or later (Express edition supported)
Built with
Claude Code
Review period
17 Nov 2026 – 17 Nov 2026
77out of 100 Passed with 5 warningsPass mark 75 and no failing check.

Scores

Security77
Code structure84
Docs & completeness79
Dependency health80
Build & deploy72
  1. AI code audit6 checks · 17 Nov 2026
  2. Installed & run17 Nov 2026
  3. Demo vs delivered17 Nov 2026
  4. Final sign-off17 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.
  • 19 of 24 promised items delivered (setup guide, example config and the rest).
  • Security scored 77/100 with no failing check.
  • 5 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 & credentialsNo API keys, private keys, SMTP passwords or live connection strings were found. The connection string uses Windows trusted auth, and SMTP and DataProtection settings are empty. The demo account password is published in the README, seed SQL and database docs, and the dev defaults enable it, so a buyer who forgets to harden it ships a known login (including Super Admin).80Warning
Dependency vulnerabilitiesEvery manifest has a lockfile (NuGet packages.lock.json per project, plus npm package-lock.json for the tracker and the web project). The e2e test project has no lockfile in the digest. The lockfile contents were not shown, so I could not confirm installed versions or check them against advisories, and no known critical vulnerability is evident.80Warning
Authorisation & access controlThe only controller shown (AuthController) uses a class-level [Authorize] with explicit [AllowAnonymous] opt-outs, rate limiting on login, Identity-based password hashing and lockout. The remaining controllers, the collector minimal-API endpoints and the ownership checks on id lookups could not be verified from the digest, and the shipped demo credentials with super-admin rights are a risk if left enabled.70Warning
Database access rulesThe project says it uses EF Core LINQ with no string-built SQL. The digest shows no raw SQL or injection path, and the schema is scripted from empty with tests that compare it to the EF model. I could not read the repositories, the SQL scripts or the maintenance procedures, so tenant scoping, foreign-key indexes and the purge procedures remain unverified.80Warning
Code structure & duplicationThe project follows a documented layering model (Domain, Application, Infrastructure, Web, Collector) with feature folders and a stated rule against business logic in controllers. The digest shows no god files or copy-pasted modules, though some demo and configuration values appear hard-coded and the full file tree could not be checked for file size.84Pass
Build reproducibilityThe solution layout, central package management, lockfiles, global.json and a Dockerfile are present, and docs describe the tracker and CSS builds. However, HowToSetup.md, the Dockerfile, the csproj files and the tests/ folder were not visible, so prerequisites, step order and the existence of referenced projects could not be confirmed.72Warning

Open warnings

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

Warning 1 No real credentials found; published demo password and weak test defaults ship to buyers

No API keys, private keys, SMTP passwords or live connection strings were found. The connection string uses Windows trusted auth, and SMTP and DataProtection settings are empty. The demo account password is published in the README, seed SQL and database docs, and the dev defaults enable it, so a buyer who forgets to harden it ships a known login (including Super Admin).

Warning 2 Lockfiles present for all manifests; npm ranges are caret-based and package contents could not be verified

Every manifest has a lockfile (NuGet packages.lock.json per project, plus npm package-lock.json for the tracker and the web project). The e2e test project has no lockfile in the digest. The lockfile contents were not shown, so I could not confirm installed versions or check them against advisories, and no known critical vulnerability is evident.

Warning 3 EF Core LINQ only by design, but SQL and schema files were not available to verify scoping or injection

The project says it uses EF Core LINQ with no string-built SQL. The digest shows no raw SQL or injection path, and the schema is scripted from empty with tests that compare it to the EF model. I could not read the repositories, the SQL scripts or the maintenance procedures, so tenant scoping, foreign-key indexes and the purge procedures remain unverified.

Warning 4 AuthController well guarded; most controllers not visible, demo credentials and public collector need review

The only controller shown (AuthController) uses a class-level [Authorize] with explicit [AllowAnonymous] opt-outs, rate limiting on login, Identity-based password hashing and lockout. The remaining controllers, the collector minimal-API endpoints and the ownership checks on id lookups could not be verified from the digest, and the shipped demo credentials with super-admin rights are a risk if left enabled.

Warning 5 Build mostly reproducible; key setup and test files could not be verified from the digest

The solution layout, central package management, lockfiles, global.json and a Dockerfile are present, and docs describe the tracker and CSS builds. However, HowToSetup.md, the Dockerfile, the csproj files and the tests/ folder were not visible, so prerequisites, step order and the existence of referenced projects could not be confirmed.

Requirement list

What the builder agreed to deliver before uploading — 19 of 24 met.

  • Complete source for every part Partial
  • No real credentials Met
  • Exactly one example config file Met
  • Database creates from empty Partial
  • HowToSetup.md for two targets Partial
  • Pinned dependencies with lockfile Partial
  • Role-gated admin and per-site data isolation Partial
  • Working live demo with sample data Met
  • CLAUDE.md for AI coding tools (nice)Met
  • Seed data and CHANGELOG (nice)Met
  • docker-compose for SQL Server and the app (nice)Met
  • Architecture docs (optional)Met
  • README.md Met
  • HowToSetup.md Met
  • NET a project file Met
  • NET a project file Met
  • a project file Met
  • JS Tracker/ Met
  • CLAUDE.md (nice)Met
  • CHANGELOG.md (nice)Met
  • a project file (nice)Met
  • docker-compose.yml (nice)Met
  • LICENSE-NOTE.md Met
  • docs/ (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 17 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 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 17 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 17 Nov 2026 with 5 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.