temporalio/temporal

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.

47 of your 141 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 11.33s · analysis 22.7s · 35.1 MB · GitHub API rate-limit (preflight)

https://github.com/temporalio/temporal · scanned 2026-06-05 20:12 UTC (4 days, 14 hours ago) · 10 languages

467 raw signals (125 security + 342 graph) 11/13 scanners ran 40th percentile · Go · huge (>500K LoC) System graph score 76 (higher by 5)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 123 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	85.0	0.20	17.00
`documentation_score`	80.0	0.15	12.00
`practices_score`	72.0	0.15	10.80
`code_quality`	70.0	0.10	7.00
Overall		1.00	80.8

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 7 High 11 Medium 6 Low 116 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 32 System graph 123 Crowd 0 Layer: Cicd 17 Quality 127 Security 8 Software 1 Hardware 1 Frontend 1

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Config drift 7 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

7 matching findings on this repo

critical Possible secret in config/development-postgres12.yaml config/development-postgres12.yaml:17
critical Possible secret in config/development-mysql-es.yaml config/development-mysql-es.yaml:17
critical Possible secret in config/development-postgres-es.yaml config/development-postgres-es.yaml:17
critical Possible secret in config/development-mysql8.yaml config/development-mysql8.yaml:17
low Very large file: common/dynamicconfig/constants.go (3413 lines)
low Very large file: common/dynamicconfig/setting_gen.go (1972 lines)
low Very large file: service/history/configs/config.go (828 lines)

View all config drift findings →

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/19ff4f2c-b153-470f-8aae-2d732aee401a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/19ff4f2c-b153-470f-8aae-2d732aee401a/

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.