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.

LIT-Protocol/flows

https://github.com/LIT-Protocol/flows · scanned 2026-06-16 04:31 UTC (2 months ago)

11 raw signals (0 security + 11 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
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 66.8/100 with 88.9% coverage. It contains 33 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 11 findings — concentrated in quality (4), hardware (3), security (2). Risk profile is high: 0 critical, 1 high, 4 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 8 of 9 actionable findings. 11 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 System graph security security conf 1.00 Insecure pattern 'new_function_used' in CLAUDE.md:19
Found a known-risky pattern (new_function_used). Review and replace if possible.
CLAUDE.md:19 New function used
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: SKILL.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.
SKILL.md VerificationSkill file
medium System graph security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: SKILL.md
Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.
SKILL.md:21 Supply chainSkill file
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 3 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 2, 11, 20
Dockerfile:2, 11, 20 (3 hits)
containersPinned dependencies
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated 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/b13ea77e-ec4b-4707-b8bf-3b2327ef9430/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b13ea77e-ec4b-4707-b8bf-3b2327ef9430/

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.