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

Scan timing: clone 2.68s · analysis 85.11s · 3.1 MB · GitHub preflight 548ms

YunYouJun/valaxy

https://github.com/YunYouJun/valaxy · scanned 2026-06-05 19:26 UTC (4 days, 16 hours ago) · 10 languages

436 raw signals (192 security + 244 graph) 5th percentile · Typescript · medium (20-100K LoC) System graph score 58 (lower by 9)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 16 hours ago · v2 · 225 actionable findings from 2 signal sources. 89 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 60.0 0.15 9.00
security_score 11.6 0.25 2.90
testing_score 46.0 0.20 9.20
documentation_score 63.0 0.15 9.45
practices_score 69.0 0.15 10.35
code_quality 71.6 0.10 7.16
Overall 1.00 48.1
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in demo/yun/valaxy.config.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in demo/yun/valaxy.config.ts:86; move to env var / secrets manager.
demo/yun/valaxy.config.ts:86
#2
Possible secret in docs/valaxy.config.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in docs/valaxy.config.ts:62; move to env var / secrets manager.
docs/valaxy.config.ts:62
#3
Possible secret in packages/valaxy/node/modules/llms/utils.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in packages/valaxy/node/modules/llms/utils.ts:267; move to env var / secrets manager.
packages/valaxy/node/modules/llms/utils.ts:267
#4
.env file present in repo: packages/devtools/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#5
Insecure pattern 'exec_used' in packages/valaxy/node/cli/utils/shortcuts.ts:58
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
packages/valaxy/node/cli/utils/shortcuts.ts:58
#6
No auth library detected
GapSeverity.MEDIUM Layer.SECURITY score 0.338
Why: medium severity
#7
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
packages/create-valaxy/template-blog/.github/workflows/gh-pages.yml:38
#8
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release-addon.yml:36
#9
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release-addon.yml
#10
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/demo.yml:39

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/eaadfe9b-d3bc-4c8a-9ba7-80ffc334d7d7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/eaadfe9b-d3bc-4c8a-9ba7-80ffc334d7d7/

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.