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.
Sign up free Scan another repo

Scan timing: clone 1.69s · analysis 0.42s · 0.6 MB · GitHub preflight 504ms

kulturpool/EDMLib

https://github.com/kulturpool/EDMLib.git · scanned 2026-05-25 08:26 UTC (1 week, 4 days ago) · 10 languages

108 findings (56 legacy + 52 scanner) 81st percentile · Python · small (2-20K LoC) Scanner says 87 (lower by 5)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 4 days ago · v2 · 82 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
85.9
/100
Repobility
85
56 legacy
9-layer
87
88.9% cov · 26 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 75.0 0.15 11.25
security_score 98.7 0.25 24.68
testing_score 100.0 0.20 20.00
documentation_score 50.0 0.15 7.50
practices_score 67.0 0.15 10.05
code_quality 80.0 0.10 8.00
Overall 1.00 81.5
Severity distribution — click a segment to filter
Active filters: layer: hardware × excluding tests × Reset all
Severity: Critical 0 High 44 Medium 3 Low 25 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 56 9-layer 26 Crowd 0 Layer: Cicd 4 Quality 57 Software 15 Api 1 Hardware 3 Frontend 1 Security 1
Scan summary Repository scanned at 86.8/100 with 88.9% coverage. It contains 240 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 26 findings — concentrated in software (12), quality (8), hardware (3). Risk profile is high: 0 critical, 1 high, 1 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 3 of 82 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high 9-layer hardware supply-chain conf 1.00 Dockerfile pipes a remote installer into a shell
Executing downloaded code during image build gives the remote endpoint build-time code execution. Prefer pinned packages or verify downloaded installers by checksum/signature.
.devcontainer/Dockerfile:17 supply-chaindockerremote-installer
low 9-layer 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.
coveragedeployment
low 9-layer hardware supply-chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12.9
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
.devcontainer/Dockerfile:1 supply-chaindockerpinned-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/6eb8cbf3-dacf-4c7a-894e-f278de8ac11c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/6eb8cbf3-dacf-4c7a-894e-f278de8ac11c/

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.