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.
Sign up free Scan another repo

toshikazu-yokoi/gx-agent-skills

https://github.com/toshikazu-yokoi/gx-agent-skills · scanned 2026-06-16 00:40 UTC (2 months, 1 week ago)

22 raw signals (0 security + 22 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
66.1
/100
Security checks
66
0 findings
System graph
66
88.9% cov · 22 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 0 Medium 15 Low 2 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 22 Crowd 0 Layer: Network 10 Frontend 1 Security 2 Quality 9
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.1/100 with 88.9% coverage. It contains 318 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 22 findings — concentrated in network (10), quality (9), security (2). Risk profile is low: 0 critical, 0 high, 15 medium. Recommended next step: open the network layer findings first — that's where the highest-impact wins live.

Showing 17 of 22 actionable findings. 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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: gx-authoring/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.
gx-authoring/SKILL.md VerificationSkill file
medium System graph quality Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in gx-authoring/scripts/detect-tooling.mjs:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
gx-authoring/scripts/detect-tooling.mjs:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in gx-kb/scripts/detect-tooling.mjs:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
gx-kb/scripts/detect-tooling.mjs:9 Node child process
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.
catalog/language/lang-data-types.yaml Ports
medium System graph network Security conf 1.00 Privileged port 12 in use
Port 12 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
catalog/language/lang-functions.yaml Ports
medium System graph network Security conf 1.00 Privileged port 13 in use
Port 13 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
catalog/language/lang-functions.yaml Ports
medium System graph network Security conf 1.00 Privileged port 14 in use
Port 14 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
catalog/language/lang-data-types.yaml Ports
medium System graph network Security conf 1.00 Privileged port 23 in use
Port 23 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
catalog/language/lang-data-picture.yaml Ports
medium System graph network Security conf 1.00 Privileged port 30 in use
Port 30 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
catalog/language/lang-data-types.yaml Ports
medium System graph network Security conf 1.00 Privileged port 35 in use
Port 35 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
catalog/language/lang-functions.yaml Ports
medium System graph network Security conf 1.00 Privileged port 45 in use
Port 45 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
catalog/language/lang-data-types.yaml Ports
medium System graph network Security conf 1.00 Privileged port 59 in use
Port 59 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
catalog/language/lang-data-picture.yaml Ports
medium System graph network Security conf 1.00 Privileged port 99 in use
Port 99 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
catalog/language/lang-data-picture.yaml Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 9 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 32 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
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/1834b760-2c26-4551-a711-9a1340626ae9/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/1834b760-2c26-4551-a711-9a1340626ae9/

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.