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.

rjxznb/dead-clock

https://github.com/rjxznb/dead-clock · scanned 2026-06-15 23:52 UTC (2 months, 3 weeks ago)

10 raw signals (0 security + 10 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 4 actionable findings from 1 signal source. 6 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

55.6% cov · 4 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 1 Low 2 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 4 Crowd 0 Layer: Frontend 1 Cicd 2 Quality 1

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 83.5/100 with 55.6% coverage. It contains 67 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 10 findings — concentrated in cicd (8), frontend (1), quality (1). Risk profile is low: 0 critical, 0 high, 5 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 3 of 4 actionable findings. 10 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 cicd CI/CD security conf 1.00 5 occurrences GitHub Action is tag-pinned rather than SHA-pinned

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

3 files, 5 locations

.github/workflows/ci.yml:25, 93 (2 hits)

.github/workflows/testflight.yml:20, 170 (2 hits)

.github/workflows/screenshots.yml:23

CI/CD securitySupply chainGithub actions

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

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

3 files, 3 locations

.github/workflows/ci.yml:79

.github/workflows/screenshots.yml:242

.github/workflows/testflight.yml:153

CI/CD securitySupply chainGithub actions

low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

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/17e38b97-1b86-4875-b743-d70d03c828ba/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/17e38b97-1b86-4875-b743-d70d03c828ba/

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.