‹ Kinroll - Membership Management SystemQuality report QR-26-00137
Kinroll - Membership Management System
Self-hosted membership system for clubs, associations and non-profits: joining, dues, member portal, email and SMS.
- Product ID
- B1042-48611
- Builder
- Atiq Rahman
- Version reviewed
- 1.0.0 · released 13 Nov 2026
- Stack
- Express 4 (API) and Next.js 16 with React 19 (web) · JavaScript (Node.js 24) with JSX, CommonJS backend · PostgreSQL 17 via Prisma 5, with Redis for job queues
- Built with
- Claude Code
- Review period
- 6 Nov 2026 – 13 Nov 2026 · 2 rounds of changes
- ✓AI code audit6 checks · 6 Nov 2026
- ✓Installed & run13 Nov 2026
- ✓Demo vs delivered13 Nov 2026
- ✓Final sign-off13 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.
- !17 of 28 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 76/100 with no failing check.
- !4 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 live API keys, private keys or production connection strings were found. The regex hits are placeholders, CI test values or code that handles passwords. Two weak-default items remain: a published demo password for the live demo (documented in README and used in an export script), and `change-me-*` JWT secrets in .env.example that pass the [hidden] minimum, so a buyer could ship them unchanged. | 88 | Warning |
| Dependency vulnerabilities | Backend, frontend and e2e each have a package-lock.json, and no wildcard or 'latest' versions appear in the manifests. Dependencies use caret ranges, which is normal, and the backend pins overrides for exceljs/unzipper and uuid. Some versions look unusual or old (Prisma 5.x, Express 4, Next.js pinned exactly), and the root has no lockfile, so this is a warning-level review rather than a failure. | 80 | Pass |
| Authorisation & access control | The visible code hashes passwords with bcrypt, applies login lockout, and separates admin access from member accounts on the user type's isMemberType flag. The digest omits the route files (admin.js, membership.js, etc.) and the controllers behind them, so per-route guards and id-based ownership checks could not be verified. The score is capped for that reason, not because a hole was found. | 70 | Warning |
| Database access rules | The visible data access goes through Prisma (findUnique, updateMany with scoped WHERE clauses), and no string-built SQL or unscoped deletes appear in the excerpts. However, the schema, migrations and most services and controllers were not included in the digest, so index, foreign-key and cascade coverage and any raw queries could not be verified. | 70 | Warning |
| Code structure & duplication | The backend separates routes, controllers, services, lib and workers with a clear layering, and the frontend splits pages from components and lib helpers. The digest shows no god files or copy-pasted modules, though the auth controllers repeat cookie and token helpers that could be shared. | 88 | Pass |
| Build reproducibility | Each package has its own package.json and lockfile, and CI, Docker and render.yaml are all present, so a clean machine can probably install and build. However, a project file points three scripts at `a project file`, which does not appear in the tree. HowToSetup.md could not be reviewed in full, so step order and prerequisite versions are unconfirmed. | 72 | Warning |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
No live API keys, private keys or production connection strings were found. The regex hits are placeholders, CI test values or code that handles passwords. Two weak-default items remain: a published demo password for the live demo (documented in README and used in an export script), and `change-me-*` JWT secrets in .env.example that pass the [hidden] minimum, so a buyer could ship them unchanged.
The visible data access goes through Prisma (findUnique, updateMany with scoped WHERE clauses), and no string-built SQL or unscoped deletes appear in the excerpts. However, the schema, migrations and most services and controllers were not included in the digest, so index, foreign-key and cascade coverage and any raw queries could not be verified.
The visible code hashes passwords with bcrypt, applies login lockout, and separates admin access from member accounts on the user type's isMemberType flag. The digest omits the route files (admin.js, membership.js, etc.) and the controllers behind them, so per-route guards and id-based ownership checks could not be verified. The score is capped for that reason, not because a hole was found.
Each package has its own package.json and lockfile, and CI, Docker and render.yaml are all present, so a clean machine can probably install and build. However, a project file points three scripts at `a project file`, which does not appear in the tree. HowToSetup.md could not be reviewed in full, so step order and prerequisite versions are unconfirmed.
Requirement list
What the builder agreed to deliver before uploading — 17 of 28 met.
- Complete source for every part Met
- Schema creates from empty Partial
- HowToSetup.md with two targets Partial
- No real credentials Met
- Single example env file Met
- Lockfiles for both apps Partial
- Authorisation on every write route Partial
- Demo account on a live URL Partial
- README with features and licence note (nice)Met
- CLAUDE.md for AI tools (nice)Met
- CHANGELOG starting at 1.0.0 (nice)Partial
- Seed data (nice)Met
- Docker compose file (nice)Met
- Automated tests (nice)Partial
- Deployment and API docs (optional)Partial
- README.md Met
- HowToSetup.md Met
- a project file Met
- Express a project filee Met
- Express a project file Met
- Next.js a project file Met
- CLAUDE.md (nice)Met
- CHANGELOG.md (nice)Met
- a project file (nice)Met
- docker-compose.yml (nice)Met
- LICENSE-NOTE.md (optional)Missing
- a project file (optional)Missing
- a project file (optional)Missing
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 13 Nov 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 13 Nov 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
- None — approved on the first round.
- Sign-off: approved for sale on 13 Nov 2026 with 4 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.