‹ DigiCardQuality report QR-26-00025
DigiCard
Digital business card platform with AI chat, event lead capture and team analytics for sales teams
- Product ID
- B0006-31698
- Builder
- Build Nest
- Version reviewed
- 1.0.0 · released 7 Oct 2026
- Stack
- ASP.NET Core 9 MVC · C# 12 / .NET 9.0 · SQL Server 2019+
- Built with
- Claude Code
- Review period
- 6 Oct 2026 – 7 Oct 2026 · 1 round of changes
- ✓AI code audit6 checks · 6 Oct 2026
- ✓Installed & run7 Oct 2026
- ✓Demo vs delivered7 Oct 2026
- ✓Final sign-off7 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.
- ✓15 of 15 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 93/100 with no failing check.
- !5 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 | No production credentials are committed. The archive correctly uses placeholders in .env.example and appsettings.example.json, and the app guards against secrets in appsettings.json at startup. Test code contains hardcoded passwords (acceptable for tests), and docker-compose.yml requires environment variables before starting. One minor concern: the seeded demo admin password 'DigiCard@2026' in a project file could be mistaken for a real default if buyers don't read the setup guide. | 92 | Warning |
| Dependency vulnerabilities | All .NET dependencies are pinned in packages.lock.json files with restore mode locked. No known critical vulnerabilities detected in the declared packages. A few packages are 1-2 minor versions behind latest (e.g., Anthropic.SDK 0.3.0 vs 0.4.x, ClosedXML 0.104.2 vs 0.104.3), but these are maintenance updates without security advisories. | 85 | Warning |
| Authorisation & access control | All mutating endpoints require authentication and appropriate role checks. Admin routes are locked to AdminOnly or SuperAdminOnly policies. Password storage uses ASP.NET Core Identity's PasswordHasher. The fallback policy denies anonymous access by default. Minor gaps: AdminContactsController detail/export endpoints lack explicit ownership checks, allowing admins to see all contacts (likely intended but undocumented). | 95 | Warning |
| Database access rules | All queries use EF Core parameterization with no string concatenation or raw SQL injection paths. Delete and update operations are properly scoped to owners or filtered by ID. The schema script is complete and can create the database from scratch. Minor issues: missing foreign key on EventContact.ContactId, and several foreign key columns lack indexes which may cause performance problems at scale. | 92 | Warning |
| Code structure & duplication | Module boundaries are well-defined with clear separation between controllers, services, and data access. However, several service files exceed 500 lines with mixed responsibilities, and there is noticeable duplication in validation logic and query patterns across multiple services. Configuration is mostly externalized but a few hard-coded values remain. | 72 | Warning |
| Build reproducibility | The solution builds cleanly with .NET 9 SDK and SQL Server. All project references resolve, Docker Compose is coherent, and lock files are present. Two minor issues: HowToSetup.md doesn't specify the exact .NET SDK version (9.0.x) before the first dotnet command, and the database upgrade script path in the changelog differs from the actual file location. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
All .NET dependencies are pinned in packages.lock.json files with restore mode locked. No known critical vulnerabilities detected in the declared packages. A few packages are 1-2 minor versions behind latest (e.g., Anthropic.SDK 0.3.0 vs 0.4.x, ClosedXML 0.104.2 vs 0.104.3), but these are maintenance updates without security advisories.
All queries use EF Core parameterization with no string concatenation or raw SQL injection paths. Delete and update operations are properly scoped to owners or filtered by ID. The schema script is complete and can create the database from scratch. Minor issues: missing foreign key on EventContact.ContactId, and several foreign key columns lack indexes which may cause performance problems at scale.
Module boundaries are well-defined with clear separation between controllers, services, and data access. However, several service files exceed 500 lines with mixed responsibilities, and there is noticeable duplication in validation logic and query patterns across multiple services. Configuration is mostly externalized but a few hard-coded values remain.
No production credentials are committed. The archive correctly uses placeholders in .env.example and appsettings.example.json, and the app guards against secrets in appsettings.json at startup. Test code contains hardcoded passwords (acceptable for tests), and docker-compose.yml requires environment variables before starting. One minor concern: the seeded demo admin password 'DigiCard@2026' in a project file could be mistaken for a real default if buyers don't read the setup guide.
All mutating endpoints require authentication and appropriate role checks. Admin routes are locked to AdminOnly or SuperAdminOnly policies. Password storage uses ASP.NET Core Identity's PasswordHasher. The fallback policy denies anonymous access by default. Minor gaps: AdminContactsController detail/export endpoints lack explicit ownership checks, allowing admins to see all contacts (likely intended but undocumented).
Requirement list
What the builder agreed to deliver before uploading — 15 of 15 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
- Authentication and roles on every mutating endpoint Met
- Pinned dependencies without critical CVEs (nice)Met
- Documentation set (nice)Met
- Working live demo 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
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 7 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 7 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 6 Oct 2026; the builder fixed them and uploaded again.
- Sign-off: approved for sale on 7 Oct 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.