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.

cloudamqp/lavinmq

https://github.com/cloudamqp/lavinmq · scanned 2026-06-17 01:49 UTC (1 month, 1 week ago)

69 raw signals (0 security + 69 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -33.4 (diff) · 33 actionable findings from 1 signal source. 36 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 · 33 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 22 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 33 Crowd 0 Layer: Frontend 1 Network 2 Hardware 13 Security 5 Cicd 3 Quality 9

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 43.3/100 with 88.9% coverage. It contains 440 nodes across 14 cross-layer flows, written primarily in mixed languages. Engine surfaced 69 findings — concentrated in cicd (38), hardware (14), quality (9). Risk profile is low: 0 critical, 0 high, 35 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 29 of 33 actionable findings. 69 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.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — static/js/helpers.js:145

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — static/js/login.js:9

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — static/js/logs.js:34

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/review-criteria.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/review-criteria.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.json

.claude/settings.json VerificationClaude instruction

medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: alpine:latest

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

packaging/alpine/Dockerfile:12 containersPinned dependencies

medium System graph hardware Supply chain conf 1.00 2 occurrences Docker base image uses a mutable or implicit tag: archlinux:latest

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

lines 1, 19

packaging/arch/Dockerfile:1, 19 (2 hits)

containersPinned dependencies

medium System graph hardware Security conf 1.00 Dockerfile runs as root: .devcontainer/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph 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.

Container

medium System graph hardware Security conf 1.00 Dockerfile runs as root: packaging/alpine/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph hardware Security conf 1.00 Dockerfile runs as root: packaging/debian/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph hardware Security conf 1.00 Dockerfile runs as root: packaging/rpm/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph cicd CI/CD security conf 1.00 9 occurrences GitHub Action is tag-pinned rather than SHA-pinned

ruby/setup-ruby@v1 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

4 files, 9 locations

.github/workflows/docker.yml:44, 54, 57, 63 (4 hits)

.github/workflows/ci.yml:348, 396, 500 (3 hits)

.github/workflows/cla.yml:30

.github/workflows/docs-check.yml:46

CI/CD securitySupply chainGithub actions

medium System graph cicd CI/CD security conf 1.00 5 occurrences 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.

5 files, 5 locations

.github/workflows/claude-code-review.yml

.github/workflows/deb.yml

.github/workflows/docker.yml

.github/workflows/docs-check.yml

.github/workflows/rpm.yml

CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in static/js/stream.js:103

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

static/js/stream.js:103 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in static/js/unacked.js:13

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

static/js/unacked.js:13 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in static/js/table.js:241

Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.

static/js/table.js:241 Insert adjacent html

medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in static/js/auth.js:39

Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.

static/js/auth.js:39 Local storage auth token

medium System graph network Security conf 1.00 Privileged port 11 in use

Port 11 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

.ameba.yml Ports

medium System graph network Security conf 1.00 Privileged port 42 in use

Port 42 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

.ameba.yml Ports

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

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

Coverage

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: 84codes/crystal:latest-alpine

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

packaging/alpine/Dockerfile:1 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: 84codes/crystal:latest-ubuntu-24.04

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

Dockerfile:2 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: 84codes/crystal:latest-ubuntu-24.04

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 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: fedora:42

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

packaging/rpm/Dockerfile:25 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: ubuntu:22.04

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

packaging/debian/Dockerfile:17 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: ubuntu:24.04

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

Dockerfile:33 containersPinned dependencies

low System graph cicd CI/CD security conf 1.00 24 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

6 files, 24 locations

.github/workflows/ci.yml:47, 88, 124, 174, 189, 201, 223, 277, +9 more (17 hits)

.github/workflows/deb.yml:34, 105 (2 hits)

.github/workflows/release.yml:15, 36 (2 hits)

.github/workflows/docker.yml:40

.github/workflows/rerun.yml:13

.github/workflows/rpm.yml:35

CI/CD securitySupply chainGithub actions

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — static/js/table.js:39

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

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/dd7b713c-ef71-4274-a9c7-6dd65bc5c17a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/dd7b713c-ef71-4274-a9c7-6dd65bc5c17a/

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.