https://github.com/shristiit/ecom
· scanned 2026-06-16 04:38 UTC (1 month, 3 weeks ago)
4 raw signals (0 security + 4 graph)
Last scanned 1 month, 3 weeks ago · v1 · 4 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.
All 15 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.
| Label | Layer | Status | Path |
|---|---|---|---|
pnpm-workspace.yaml |
software | healthy | pnpm-workspace.yaml |
CODEX_STRIPE_FIX_PROMPT.md |
software | healthy | CODEX_STRIPE_FIX_PROMPT.md |
STRIPE_PAYMENT_INTEGRATION_ANALYSIS.md |
software | healthy | STRIPE_PAYMENT_INTEGRATION_ANALYSIS.md |
STRIPE_FRONTEND_ANALYSIS.md |
software | healthy | STRIPE_FRONTEND_ANALYSIS.md |
STRIPE_INTEGRATION_ISSUES_MASTER_LIST.md |
software | healthy | STRIPE_INTEGRATION_ISSUES_MASTER_LIST.md |
README.md |
software | healthy | README.md |
ANALYSIS_SUMMARY.md |
software | healthy | ANALYSIS_SUMMARY.md |
DEPLOYMENT_AWS.md |
software | healthy | DEPLOYMENT_AWS.md |
package.json |
software | healthy | package.json |
LOCAL_DEV_ENV.md |
software | healthy | LOCAL_DEV_ENV.md |
DEPLOYMENT_EC2.md |
software | healthy | DEPLOYMENT_EC2.md |
turbo.json |
software | healthy | turbo.json |
pnpm-lock.yaml |
software | healthy | pnpm-lock.yaml |
| Label | Layer | Status | Path |
|---|---|---|---|
shristiit__ecom |
software | healthy | /data/fable5_failed_archive/shristiit__ecom |
| Label | Layer | Status | Path |
|---|---|---|---|
vps::aws |
hardware | healthy | README.md |
This page is publicly accessible at:
https://repobility.com/scan/cc8f0fc0-228d-4c44-a016-7cb8271151b7/
To check status programmatically (no auth required):
curl -s https://repobility.com/api/v1/public/scan/cc8f0fc0-228d-4c44-a016-7cb8271151b7/
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.