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

Scan timing: clone 2.98s · analysis 7.47s · 6.4 MB · GitHub preflight 433ms

CloakBrowser

https://github.com/CloakHQ/CloakBrowser · scanned 2026-06-01 20:50 UTC (3 days, 17 hours ago) · 10 languages

632 findings (127 legacy + 505 scanner) 86th percentile · Python · medium (20-100K LoC) Scanner says 84 (lower by 2)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 3 days, 17 hours ago · v8 · 191 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
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 75.0 0.15 11.25
security_score 74.2 0.25 18.55
testing_score 100.0 0.20 20.00
documentation_score 97.0 0.15 14.55
practices_score 80.0 0.15 12.00
code_quality 48.5 0.10 4.85
Overall 1.00 81.2
Severity distribution — click a segment to filter
Active filters: layer: hardware × excluding tests × Reset all
Scan summary Repository scanned at 83.7/100 with 88.9% coverage. It contains 1373 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 64 findings — concentrated in software (24), quality (21), frontend (10). Risk profile is low: 0 critical, 0 high, 6 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

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

medium 9-layer hardware supply-chain conf 1.00 Docker base image uses a mutable or implicit tag: cloakhq/cloakbrowser:latest
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
examples/integrations/aws_lambda/Dockerfile:35 supply-chaindockerpinned-dependencies
medium 9-layer hardware supply-chain conf 1.00 Dockerfile ADD downloads remote content without checksum
Remote build inputs can change or be replaced upstream. Use Dockerfile ADD --checksum or download with an explicit digest/signature verification step.
examples/integrations/aws_lambda/Dockerfile:45 supply-chaindockerchecksum
medium 9-layer hardware security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
securitycontainer
medium 9-layer hardware security conf 1.00 Dockerfile runs as root: examples/integrations/aws_lambda/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
securitycontainer
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-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: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/efda4189-83a6-40d4-9858-3ed2e14aae56/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/efda4189-83a6-40d4-9858-3ed2e14aae56/

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.