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.

zaitsu82/komine-crm-backend

https://github.com/zaitsu82/komine-crm-backend · scanned 2026-06-16 01:10 UTC (2 months, 1 week ago)

132 raw signals (0 security + 132 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 110 actionable findings from 1 signal source. 22 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 110 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 1 Medium 5 Low 88 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 110 Crowd 0 Layer: Frontend 28 Network 2 Hardware 3 Security 3 Cicd 4 Quality 20 Api 50

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 33.0/100 with 100.0% coverage. It contains 1256 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 132 findings — concentrated in api (50), frontend (28), quality (20). Risk profile is high: 8 critical, 3 high, 6 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 96 of 110 actionable findings. 132 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.

critical System graph security Secrets conf 1.00 3 occurrences Possible secret in src/utils/sentry.ts

Detected pattern matching password_literal. Rotate the credential and move to a secret manager.

lines 77, 80, 83

src/utils/sentry.ts:77, 80, 83 (3 hits)

critical System graph security Secrets conf 1.00 Runtime dotenv file present in repo: .env.render

`.env.render` looks like a runtime dotenv file. It contains secret-looking assignments for SUPABASE_SERVICE_ROLE_KEY. Move real values to a secret manager and keep only `.env.example` style templates in source control.

.env.render ConfigEnv fileRuntime env

high System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action tracks a moving branch

aquasecurity/trivy-action@master can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

lines 153, 181, 192

.github/workflows/ci.yml:153, 181, 192 (3 hits)

CI/CD securitySupply chainGithub actions

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.

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

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

lines 173, 239

.github/workflows/ci.yml:173, 239 (2 hits)

CI/CD securitySupply chainGithub actions

medium System graph network Security conf 1.00 Privileged port 10 in use

Port 10 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

swagger.yaml Ports

medium System graph network Security conf 1.00 Privileged port 12 in use

Port 12 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

swagger.yaml Ports

low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found

Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.

Deployment

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

Found 161 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 3 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-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 4, 31, 70

Dockerfile:4, 31, 70 (3 hits)

containersPinned dependencies

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-slim

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

Dockerfile:104 containersPinned dependencies

low System graph cicd CI/CD security conf 1.00 13 occurrences GitHub Action is tag-pinned rather than SHA-pinned

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

lines 22, 30, 45, 58, 66, 87, 95, 116, +5 more

.github/workflows/ci.yml:22, 30, 45, 58, 66, 87, 95, 116, +5 more (13 hits)

CI/CD securitySupply chainGithub actions

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 Integrity conf 1.00 Old/deprecated-named symbol `skipLegacy` in scripts/verify-migration.ts:87

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `withLegacy` in scripts/investigate-payment.ts:13

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts

preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.

package.json CI/CD securitySupply chainNpm

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 — prisma/seed.ts:106