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

Scan timing: clone 3.62s · analysis 49.74s · 3.2 MB · GitHub API rate-limit (preflight)

dsgnr/portchecker.io

https://github.com/dsgnr/portchecker.io · scanned 2026-06-05 23:59 UTC (4 days, 1 hour ago) · 10 languages

144 raw signals (94 security + 50 graph) 55th percentile · Python · small (2-20K LoC) System graph score 82 (lower by 11)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 1 hour ago · v2 · 96 actionable findings from 2 signal sources. 23 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 55.0 0.15 8.25
security_score 27.3 0.25 6.83
testing_score 100.0 0.20 20.00
documentation_score 90.0 0.15 13.50
practices_score 92.0 0.15 13.80
code_quality 79.4 0.10 7.94
Overall 1.00 70.3
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Scan summary Quality grade B (70/100). Dimensions: security 27, maintainability 55. 94 findings (37 security). 2,116 lines analyzed.

Showing 67 of 96 actionable findings. 119 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.

high Security checks software dependencies conf 0.90 ✓ Repobility 7 occurrences Dockerfile FROM `python:3.13-alpine3.23` not pinned by digest
`FROM python:3.13-alpine3.23` 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.
4 files, 7 locations
backend/Dockerfile:1, 14 (2 hits)
backend/Dockerfile.dev:1, 14 (2 hits)
frontend/Dockerfile:1, 12 (2 hits)
frontend/Dockerfile.dev:1
low Security checks cicd CI/CD security conf 0.90 ✓ Repobility 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
Action `actions/checkout` pinned to mutable ref `@v4` uses a mutable tag or branch. Pin external actions to a reviewed full commit SHA when the workflow is security-sensitive.
2 files, 4 locations
.github/workflows/codeql-analysis.yml:31 (2 hits)
.github/workflows/ghcr-tag-build.yml:24 (2 hits)
CI/CD securitySupply chainGitHub Actions
medium Security checks cicd CI/CD security conf 0.90 ✓ Repobility 6 occurrences GitHub Action is tag-pinned rather than SHA-pinned
Action `github/codeql-action/init` pinned to mutable ref `@v3` uses a mutable tag or branch. Pin external actions to a reviewed full commit SHA when the workflow is security-sensitive.
lines 34, 39, 42
.github/workflows/codeql-analysis.yml:34, 39, 42 (6 hits)
CI/CD securitySupply chainGitHub Actions
high Security checks software dependencies conf 0.88 minimatch: GHSA-23c5-xmqv-rm74
minimatch ReDoS: nested *() extglobs generate catastrophically backtracking regular expressions
frontend/web/yarn.lock
high Security checks software dependencies conf 0.88 minimatch: GHSA-3ppc-4f35-3m26
minimatch has a ReDoS via repeated wildcards with non-matching literal in pattern
frontend/web/yarn.lock
high Security checks software dependencies conf 0.88 minimatch: GHSA-7r86-cg39-jmmj
minimatch has ReDoS: matchOne() combinatorial backtracking via multiple non-adjacent GLOBSTAR segments
frontend/web/yarn.lock
high Security checks software dependencies conf 0.88 path-to-regexp: GHSA-37ch-88jc-xwx2
path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters
frontend/web/yarn.lock
high Security checks software dependencies conf 0.88 picomatch: GHSA-c2c7-rcm5-vvqj
Picomatch has a ReDoS vulnerability via extglob quantifiers
frontend/web/yarn.lock
high Security checks software dependencies conf 0.90 ✓ Repobility 3 occurrences pre-commit hook `https://github.com/pre-commit/pre-commit-hooks` pinned to mutable rev `v5.0.0`
`.pre-commit-config.yaml` references `https://github.com/pre-commit/pre-commit-hooks` at `rev: v5.0.0`. If `{rev}` is a branch or version tag, the repo owner can push new code there and `pre-commit install --install-hooks` will fetch it on every developer's machine.
lines 6, 18, 24
.pre-commit-config.yaml:6, 18, 24 (3 hits)
high Security checks software dependencies conf 0.88 serialize-javascript: GHSA-5c6j-r48x-rmvq
Serialize JavaScript is Vulnerable to RCE via RegExp.flags and Date.prototype.toISOString()
frontend/web/yarn.lock
high Security checks software dependencies conf 0.88 serialize-javascript: GHSA-hxcc-f52p-wc94
Insecure serialization leading to RCE in serialize-javascript
frontend/web/yarn.lock
medium Security checks security auth conf 0.92 [AUC001] No Repobility access matrix policy found: The repository uses web/API frameworks but does not define .repobility/access.yml or equivalent authorization documentation.
The repository uses web/API frameworks but does not define .repobility/access.yml or equivalent authorization documentation.
medium Security checks software dependencies conf 0.88 ajv: GHSA-2g4f-4pwh-qvx6
ajv has ReDoS when using `$data` option
frontend/web/yarn.lock
medium Security checks software dependencies conf 0.88 brace-expansion: GHSA-f886-m6hf-6m8v
brace-expansion: Zero-step sequence causes process hang and memory exhaustion
frontend/web/yarn.lock
medium Security checks cicd CI/CD security conf 0.94 2 occurrences Compose service `web` image uses the latest tag
The latest tag is mutable and can change without a code review, producing different images from the same source.
lines 2, 21
docker-compose.yml:2, 21 (2 hits)
CI/CD securitycontainers
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 4 occurrences Docker final stage has no non-root USER
Docker images run as root unless the image or Dockerfile switches to a non-root user.
4 files, 4 locations
backend/Dockerfile:15
backend/Dockerfile.dev:15
frontend/Dockerfile:12
frontend/Dockerfile.dev:1
CI/CD securitycontainers
medium Security checks software dependencies conf 0.88 picomatch: GHSA-3v7f-55p6-f55p
Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching
frontend/web/yarn.lock
medium Security checks quality Quality conf 0.78 Public web service has no security.txt
security.txt gives researchers and customers a safe disclosure channel. Public web apps and APIs should publish it under /.well-known/security.txt.
.well-known/security.txt
medium Security checks software dependencies conf 0.90 Python package `certifi` is 1 major version(s) behind (2025.1.31 -> 2026.5.20)
poetry.lock pins `certifi` at 2025.1.31 but the latest stable release on PyPI is 2026.5.20 (1 major version(s) behind).
backend/poetry.lock
medium Security checks software dependencies conf 0.90 Python package `faker` is 3 major version(s) behind (37.0.1 -> 40.21.0)
poetry.lock pins `faker` at 37.0.1 but the latest stable release on PyPI is 40.21.0 (3 major version(s) behind).
backend/poetry.lock
medium Security checks software dependencies conf 0.90 Python package `markdown-it-py` is 1 major version(s) behind (3.0.0 -> 4.2.0)
poetry.lock pins `markdown-it-py` at 3.0.0 but the latest stable release on PyPI is 4.2.0 (1 major version(s) behind).
backend/poetry.lock
medium Security checks software dependencies conf 0.90 Python package `packaging` is 2 major version(s) behind (24.2 -> 26.2)
poetry.lock pins `packaging` at 24.2 but the latest stable release on PyPI is 26.2 (2 major version(s) behind).
backend/poetry.lock
medium Security checks software dependencies conf 0.90 Python package `polyfactory` is 1 major version(s) behind (2.19.0 -> 3.3.0)
poetry.lock pins `polyfactory` at 2.19.0 but the latest stable release on PyPI is 3.3.0 (1 major version(s) behind).
backend/poetry.lock
medium Security checks software dependencies conf 0.90 Python package `rich` is 2 major version(s) behind (13.9.4 -> 15.0.0)
poetry.lock pins `rich` at 13.9.4 but the latest stable release on PyPI is 15.0.0 (2 major version(s) behind).
backend/poetry.lock
medium Security checks software dependencies conf 0.90 Python package `tzdata` is 1 major version(s) behind (2025.1 -> 2026.2)
poetry.lock pins `tzdata` at 2025.1 but the latest stable release on PyPI is 2026.2 (1 major version(s) behind).
backend/poetry.lock
medium Security checks software dependencies conf 0.88 qs: GHSA-q8mj-m7cp-5q26
qs has a remotely triggerable DoS: qs.stringify crashes with TypeError on null/undefined entries in comma-format arrays when encodeValuesOnly is set
frontend/web/yarn.lock
medium Security checks software dependencies conf 0.88 serialize-javascript: GHSA-h9rv-jmmf-4pgx
Cross-Site Scripting in serialize-javascript
frontend/web/yarn.lock
medium Security checks software dependencies conf 0.88 uuid: GHSA-w5hq-g745-h8pq
uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided
frontend/web/yarn.lock
medium Security checks software dependencies conf 0.88 ws: GHSA-58qx-3vcg-4xpx
ws: Uninitialized memory disclosure
frontend/web/yarn.lock
medium System graph hardware Security conf 1.00 Dockerfile runs as root: backend/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: frontend/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 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/dependabot-auto-merge.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 security auth conf 0.76 [AUC005] No authorization-focused tests detected: No test files with common authorization, ownership, 403, admin, or super_admin assertions were found.
No test files with common authorization, ownership, 403, admin, or super_admin assertions were found.
high Security checks cicd CI/CD security conf 0.56 2 occurrences Compose service does not declare a runtime user
If the image does not define USER internally, this service may run as root.
lines 2, 21
docker-compose.yml:2, 21 (2 hits)
CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.62 2 occurrences Compose service lacks no-new-privileges hardening
no-new-privileges prevents processes from gaining additional privileges through setuid binaries or file capabilities.
lines 2, 21
docker-compose.yml:2, 21 (2 hits)
CI/CD securitycontainers
low Security checks quality Quality conf 0.60 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.
backend/api/app/routes/v2.py:66 duplicationquality
low Security checks software dependencies conf 0.90 npm package `globals` is minor version(s) behind (^17.4.0 -> 17.6.0)
`globals` is pinned/resolved at ^17.4.0 but the latest stable release on the npm registry is 17.6.0 (minor version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.
frontend/web/package.json
low Security checks software dependencies conf 0.90 Python package `anyio` is minor version(s) behind (4.9.0 -> 4.13.0)
poetry.lock pins `anyio` at 4.9.0 but the latest stable release on PyPI is 4.13.0 (minor version(s) behind).
backend/poetry.lock
low Security checks software dependencies conf 0.90 Python package `astroid` is minor version(s) behind (4.0.2 -> 4.1.2)
poetry.lock pins `astroid` at 4.0.2 but the latest stable release on PyPI is 4.1.2 (minor version(s) behind).
backend/poetry.lock
low Security checks software dependencies conf 0.90 Python package `click` is minor version(s) behind (8.1.8 -> 8.4.1)
poetry.lock pins `click` at 8.1.8 but the latest stable release on PyPI is 8.4.1 (minor version(s) behind).
backend/poetry.lock
low Security checks software dependencies conf 0.90 Python package `dill` is minor version(s) behind (0.3.9 -> 0.4.1)
poetry.lock pins `dill` at 0.3.9 but the latest stable release on PyPI is 0.4.1 (minor version(s) behind).
backend/poetry.lock
low Security checks software dependencies conf 0.90 Python package `httpx` is minor version(s) behind (0.25.1 -> 0.28.1)
poetry.lock pins `httpx` at 0.25.1 but the latest stable release on PyPI is 0.28.1 (minor version(s) behind).
backend/poetry.lock
low Security checks software dependencies conf 0.90 Python package `idna` is minor version(s) behind (3.15 -> 3.18)
poetry.lock pins `idna` at 3.15 but the latest stable release on PyPI is 3.18 (minor version(s) behind).
backend/poetry.lock
low Security checks software dependencies conf 0.90 Python package `iniconfig` is minor version(s) behind (2.0.0 -> 2.3.0)
poetry.lock pins `iniconfig` at 2.0.0 but the latest stable release on PyPI is 2.3.0 (minor version(s) behind).
backend/poetry.lock
low Security checks software dependencies conf 0.90 Python package `litestar-htmx` is minor version(s) behind (0.4.1 -> 0.5.0)
poetry.lock pins `litestar-htmx` at 0.4.1 but the latest stable release on PyPI is 0.5.0 (minor version(s) behind).
backend/poetry.lock
low Security checks software dependencies conf 0.90 Python package `msgspec` is minor version(s) behind (0.19.0 -> 0.21.1)
poetry.lock pins `msgspec` at 0.19.0 but the latest stable release on PyPI is 0.21.1 (minor version(s) behind).
backend/poetry.lock
low Security checks software dependencies conf 0.90 Python package `multipart` is minor version(s) behind (1.2.2 -> 1.3.1)
poetry.lock pins `multipart` at 1.2.2 but the latest stable release on PyPI is 1.3.1 (minor version(s) behind).
backend/poetry.lock
low Security checks software dependencies conf 0.90 Python package `platformdirs` is minor version(s) behind (4.3.6 -> 4.10.0)
poetry.lock pins `platformdirs` at 4.3.6 but the latest stable release on PyPI is 4.10.0 (minor version(s) behind).
backend/poetry.lock
low Security checks software dependencies conf 0.90 Python package `pluggy` is minor version(s) behind (1.5.0 -> 1.6.0)
poetry.lock pins `pluggy` at 1.5.0 but the latest stable release on PyPI is 1.6.0 (minor version(s) behind).
backend/poetry.lock
low Security checks software dependencies conf 0.90 Python package `prometheus-client` is minor version(s) behind (0.21.1 -> 0.25.0)
poetry.lock pins `prometheus-client` at 0.21.1 but the latest stable release on PyPI is 0.25.0 (minor version(s) behind).
backend/poetry.lock
low Security checks software dependencies conf 0.90 Python package `rich-click` is minor version(s) behind (1.8.8 -> 1.9.8)
poetry.lock pins `rich-click` at 1.8.8 but the latest stable release on PyPI is 1.9.8 (minor version(s) behind).
backend/poetry.lock
low Security checks software dependencies conf 0.90 Python package `tomlkit` is minor version(s) behind (0.13.2 -> 0.15.0)
poetry.lock pins `tomlkit` at 0.13.2 but the latest stable release on PyPI is 0.15.0 (minor version(s) behind).
backend/poetry.lock
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: nginx:stable-alpine-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
frontend/Dockerfile:12 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:25-alpine3.22
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
frontend/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.13-alpine3.23
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, 14
backend/Dockerfile:1, 14 (2 hits)
containersPinned dependencies
low System graph software Dead code candidate conf 1.00 File has no detected symbols: frontend/web/browser-tests/checker.spec.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: frontend/web/jest.config.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: frontend/web/playwright.config.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: frontend/web/src/__tests__/setup.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: frontend/web/webpack.config.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/api/app/routes/v2.py:query_post, backend/api/app/routes/v1.py:v1_query_post This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_query_post_endpoint_v1` in backend/tests/test_api_routes.py:61
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/web/src/__tests__/index.test.js:254
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
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/web/src/js/index.js:149
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/32efe60e-cc3a-45bd-b1b0-9166304b5d82/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/32efe60e-cc3a-45bd-b1b0-9166304b5d82/

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.