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

xiaojilele-glitch/WhyBuddy

https://github.com/xiaojilele-glitch/WhyBuddy · scanned 2026-06-16 04:41 UTC (1 month, 2 weeks ago)

7 raw signals (0 security + 7 graph)

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

Complete repo analysis

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

JSON
Combined
91.1
/100
Security checks
91
0 findings
System graph
91
88.9% cov · 6 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 2 Low 2 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 6 Crowd 0 Layer: Hardware 2 Frontend 1 Security 1 Quality 2

All 42 nodes from the latest scan, grouped by kind. Each node is a unit the engine identified (file, function, endpoint, table…). Most users won't need this view — it's primarily for debugging the engine's graph extraction or for AI agents that want to enumerate the project structure.

LabelLayerStatusPath
.env.example software healthy .env.example
tsconfig.node.json software healthy tsconfig.node.json
CONTRIBUTING.md software healthy CONTRIBUTING.md
CHANGELOG.md software healthy CHANGELOG.md
vite.config.ts software healthy vite.config.ts
ROADMAP.md software healthy ROADMAP.md
package-lock.json software healthy package-lock.json
README.zh-CN.md software healthy README.zh-CN.md
README.md software healthy README.md
SECURITY.md software healthy SECURITY.md
vitest.config.server.ts software healthy vitest.config.server.ts
LICENSE software healthy LICENSE
vitest.setup.ts software healthy vitest.setup.ts
README.new.md software healthy README.new.md
docker-compose.yml software healthy docker-compose.yml
package.json software healthy package.json
CODE_OF_CONDUCT.md software healthy CODE_OF_CONDUCT.md
components.json software healthy components.json
GROK_PLANS_EXPORT_README.md software healthy GROK_PLANS_EXPORT_README.md
Dockerfile software healthy Dockerfile
pnpm-lock.yaml software healthy pnpm-lock.yaml
tsconfig.json software healthy tsconfig.json
codeflow-report.md software healthy codeflow-report.md

LabelLayerStatusPath
ensureLogDir software healthy vite.config.ts:ensureLogDir
trimLogFile software healthy vite.config.ts:trimLogFile
writeToLogFile software healthy vite.config.ts:writeToLogFile
vitePluginManusDebugCollector software healthy vite.config.ts:vitePluginManusDebugCollector
handlePayload software healthy vite.config.ts:handlePayload
reqBody software healthy vite.config.ts:reqBody

LabelLayerStatusPath
image::Dockerfile hardware healthy Dockerfile
mysql hardware healthy docker-compose.yml
app hardware healthy docker-compose.yml

LabelLayerStatusPath
mysql data healthy .env.example
redis data healthy .env.example

LabelLayerStatusPath
port:3001 network healthy .env.example
port:3000 network healthy vite.config.ts

LabelLayerStatusPath
vps::azure hardware healthy .env.example
vps::aws hardware healthy pnpm-lock.yaml

LabelLayerStatusPath
xiaojilele-glitch__WhyBuddy software healthy /data/fable5_failed_archive/xiaojilele-glitch__WhyBuddy

LabelLayerStatusPath
USE /__manus__/logs api healthy vite.config.ts

LabelLayerStatusPath
127.0.0.1 network healthy .env.example

LabelLayerStatusPath
gpu (detected) hardware healthy pnpm-lock.yaml
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/eecab007-27b6-4fb4-b23c-572ffc61bae8/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/eecab007-27b6-4fb4-b23c-572ffc61bae8/

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.