Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

DennisSiersma/kingen

https://github.com/DennisSiersma/kingen · scanned 2026-06-17 01:26 UTC (1 month, 2 weeks ago)

22 raw signals (0 security + 22 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ +7.4 (diff) · 21 actionable findings from 1 signal source. 1 repeated signal grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 21 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 11 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 21 Crowd 0 Layer: Frontend 3 Hardware 2 Security 5 Cicd 1 Quality 10

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 84.1/100 with 77.8% coverage. It contains 362 nodes across 1 cross-layer flows, written primarily in mixed languages. Engine surfaced 22 findings — concentrated in quality (10), security (5), frontend (3). Risk profile is low: 0 critical, 0 high, 11 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 19 of 21 actionable findings. 22 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, ci, tests, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/online.ts:281

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

packages/client/src/online.ts:281 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/ui/hud.ts:316

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

packages/client/src/ui/hud.ts:316 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/ui/scoreboard.ts:78

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

packages/client/src/ui/scoreboard.ts:78 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/ui/setup.ts:142

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

packages/client/src/ui/setup.ts:142 Direct innerhtml assignment

medium System graph security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected

No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.

CI/CD securityCoverage

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 13 placeholder/mock markers across 7 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

2 test file(s) for 42 source file(s) (ratio 0.05). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 16 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.

CleanupRepo hardeningGenerated repo pattern

low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:22-alpine

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

lines 8, 24

Dockerfile:8, 24 (2 hits)

containersPinned dependencies

low System graph quality License conf 1.00 No license file detected

No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.

Repo hardeningGenerated repo pattern

low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/client/package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

packages/client/package.json LockfileReproducibilityGenerated repo pattern

low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/server/package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

packages/server/package.json LockfileReproducibilityGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/server/src/index.ts:72

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/server/src/integration.test-manual.ts:127

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/shared/src/games/kingen/engine.test-manual.ts:218

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/0e8380f6-8fd3-46fa-94fa-ee1f910bda68/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0e8380f6-8fd3-46fa-94fa-ee1f910bda68/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.