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.
18 of your 29 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 3.91s · analysis 2.04s · 15.4 MB · GitHub API rate-limit (preflight)

zivillian/ism7mqtt

https://github.com/zivillian/ism7mqtt · scanned 2026-06-05 18:31 UTC (4 days, 18 hours ago) · 10 languages

59 raw signals (29 security + 30 graph) System graph score 81 (lower by 20)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 18 hours ago · v2 · 15 actionable findings from 2 signal sources. 29 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 80.0 0.15 12.00
security_score 86.3 0.25 21.57
testing_score 0.0 0.20 0.00
documentation_score 60.0 0.15 9.00
practices_score 75.0 0.15 11.25
code_quality 75.5 0.10 7.55
Overall 1.00 61.4
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Scan summary Quality grade C+ (61/100). Dimensions: security 86, maintainability 80. 29 findings (18 security). 5,098 lines analyzed.

Showing 12 of 15 actionable findings. 44 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 Security checks security secrets conf 0.95 Found a PKCS #12 file, which commonly contain bundled private keys.
Gitleaks detected a committed secret or credential pattern.
src/ism7ssl/Resources/client.pfx
high Security checks software dependencies conf 0.90 ✓ Repobility Dockerfile FROM `mcr.microsoft.com/dotnet/runtime-deps:10.0-alpine` not pinned by digest
`FROM mcr.microsoft.com/dotnet/runtime-deps:10.0-alpine` resolves the tag at build time. The registry CAN re-push a different image for the same tag, so every build is potentially different. Production images should pin to `image@sha256:...` for reproducibility + supply-chain integrity.
Dockerfile:18
low Security checks cicd CI/CD security conf 0.90 ✓ Repobility 20 occurrences GitHub Action is tag-pinned rather than SHA-pinned
Action `actions/checkout` pinned to mutable ref `@v6` uses a mutable tag or branch. Pin external actions to a reviewed full commit SHA when the workflow is security-sensitive.
3 files, 20 locations
.github/workflows/dotnet.yml:15, 19, 48, 52, 56, 60, 64, 68, +6 more (15 hits)
.github/workflows/release.yml:14, 18 (3 hits)
.github/workflows/docker.yml:14 (2 hits)
CI/CD securitySupply chainGitHub Actions
medium Security checks cicd CI/CD security conf 0.90 Docker build context has no .dockerignore
Without .dockerignore, build context can include source history, local env files, dependencies, and generated artifacts.
.dockerignore CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.82 Docker final stage has no non-root USER
Docker images run as root unless the image or Dockerfile switches to a non-root user.
Dockerfile:19 CI/CD securitycontainers
medium System graph cicd CI/CD security conf 1.00 5 occurrences GitHub Action is tag-pinned rather than SHA-pinned
docker/setup-qemu-action@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 23, 25, 27, 33, 37
.github/workflows/docker.yml:23, 25, 27, 33, 37 (5 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
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.). Either auth lives in custom code, in a separate service, or is missing.
auth
low Security checks quality Quality conf 0.60 7 occurrences Duplicated implementation block across source files
Duplicate implementation blocks are maintenance debt. Keep them visible, but they are not a high-severity defect unless the duplicated logic is security-sensitive or drifting.
6 files, 7 locations
src/ism7ssl/Resources.Designer.cs:3, 5 (2 hits)
src/ism7mqtt/ISM7/Protocol/InfonumberWriteResp.cs:7
src/ism7mqtt/ISM7/Xml/BM2TimeConverterTemplate.cs:13
src/ism7mqtt/ISM7/Xml/Bit4to7ConverterTemplate.cs:15
src/ism7mqtt/Resources.Designer.cs:3
src/ism7proxy/Resources.Designer.cs:5
duplicationquality
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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: mcr.microsoft.com/dotnet/runtime-deps:10.0-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:18 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: mcr.microsoft.com/dotnet/sdk:10.0
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:1 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/bd400ede-78cf-4440-8677-98efab2eafde/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/bd400ede-78cf-4440-8677-98efab2eafde/

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.