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.

NickLaye/amocrm-health-monitor

https://github.com/NickLaye/amocrm-health-monitor · scanned 2026-06-16 04:34 UTC (1 month, 4 weeks ago)

8 raw signals (0 security + 8 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 6 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 1 Medium 1 Low 2 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 6 Crowd 0 Layer: Api 1 Hardware 1 Security 2 Quality 2

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

Showing 5 of 6 actionable findings. 8 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 Runtime dotenv file present in repo: .env.production.old

`.env.production.old` looks like a runtime dotenv file. It contains secret-looking assignments for AMOCRM_ACCESS_TOKEN, AMOCRM_CLIENT_SECRET, AMOCRM_REFRESH_TOKEN, API_SECRET. Move real values to a secret manager and keep only `.env.example` style templates in source control.

.env.production.old ConfigEnv fileRuntime env

high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: .env.local.backup.2025-12-02-2246

`.env.local.backup.2025-12-02-2246` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.

.env.local.backup.2025-12-02-2246 ConfigEnv fileRuntime env

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

0 test file(s) for 3 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

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

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

Repo 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:18-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, 24, 38

Dockerfile:4, 24, 38 (3 hits)

containersPinned dependencies

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/00413b4d-9829-4dc3-870c-974436957cc1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/00413b4d-9829-4dc3-870c-974436957cc1/

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.