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.

jacobpeart-cyber/pysoar

https://github.com/jacobpeart-cyber/pysoar · scanned 2026-06-16 04:28 UTC (2 months ago)

6 raw signals (0 security + 6 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months ago · v1 · 5 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

66.7% cov · 5 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 0 Medium 0 Low 3 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 5 Crowd 0 Layer: 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 75.6/100 with 66.7% coverage. It contains 53 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 6 findings — concentrated in hardware (2), security (2), quality (2). Risk profile is high: 2 critical, 0 high, 0 medium. Recommended next step: open the hardware layer findings first — that's where the highest-impact wins live.

Showing 5 of 5 actionable findings. 6 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.bak

`.env.bak` looks like a runtime dotenv file. It contains secret-looking assignments for SECRET_KEY, JWT_SECRET_KEY, ADMIN_PASSWORD, POSTGRES_PASSWORD, ENCRYPTION_MASTER_KEY. Move real values to a secret manager and keep only `.env.example` style templates in source control.

.env.bak ConfigEnv fileRuntime env

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

`.env.production` looks like a runtime dotenv file. It contains secret-looking assignments for FIRST_ADMIN_PASSWORD, MISP_API_KEY, PAGERDUTY_API_KEY, ELASTICSEARCH_PASSWORD, SPLUNK_HEC_TOKEN. Move real values to a secret manager and keep only `.env.example` style templates in source control.

.env.production ConfigEnv fileRuntime env

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

Multiple low-cost hardening controls are missing together: license, ci. 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 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.11-slim

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

lines 5, 25

Dockerfile:5, 25 (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

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/af8f2ae4-5b9f-4fd3-aaf1-406132e4cb82/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/af8f2ae4-5b9f-4fd3-aaf1-406132e4cb82/

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.