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.

sebkabyte/Pacjent360

https://github.com/sebkabyte/Pacjent360 · scanned 2026-06-16 00:06 UTC (2 months, 2 weeks ago)

39 raw signals (0 security + 39 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 38 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 · 38 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 9 Low 27 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 38 Crowd 0 Layer: Frontend 21 Security 8 Cicd 1 Quality 8

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 95.6/100 with 77.8% coverage. It contains 855 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 39 findings — concentrated in frontend (21), security (8), quality (8). Risk profile is low: 0 critical, 0 high, 9 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 36 of 38 actionable findings. 39 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 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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/app.js:1521

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

public/app.js:1521 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/assets/story.js:248

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

public/assets/story.js:248 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/capture-screens.js:1

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

tools/capture-screens.js:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/release-readiness.js:3

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

tools/release-readiness.js:3 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/smoke-browser.js:1

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

tools/smoke-browser.js:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/verify-click-routes.js:1

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

tools/verify-click-routes.js:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/verify-reactivity.js:1

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

tools/verify-reactivity.js:1 Node child process

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

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

Found 48 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 cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

lines 21, 24

.github/workflows/validate.yml:21, 24 (2 hits)

CI/CD securitySupply chainGithub actions

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

7 tests / 31 src (ratio 0.23).

low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tools/capture-screens.js:310