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.

dquillman/cipher-marketing

https://github.com/dquillman/cipher-marketing · scanned 2026-06-17 01:58 UTC (1 month, 1 week ago)

76 raw signals (0 security + 76 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ +1.5 (diff) · 76 actionable findings from 1 signal source. 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

Last 2 scans of this repo. Each new scan persists a full payload — historical comparison is exact, not lossy.

v1
Jun 16 03:57
v2
Jun 17 01:58
Diff: previous → latest scan
Score Δ
1.50
Gaps added
76
Gaps resolved
0
Edges changed
+241 / -0
New gaps in latest scan:
  • No frontend routes/components detected info
  • Insecure pattern 'node_child_process' in serve.mjs:14 medium
  • Insecure pattern 'cors_wildcard' in serve.mjs:52 medium
  • Possible secret in scripts/write-competitor-intel.mjs critical
  • Possible secret in scripts/regrade-mon-launch.mjs critical
  • + 71 more
v#IDStatusScoreGapsNodesCommitStarted
v scan_88c77e107d0c ok 78.2 76 264 Jun 17 01:58
v scan_261786ba718a ok 76.7 1 Jun 16 03:57
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/0cdaa5ff-0501-4d8f-9b14-d4ac1d40e524/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0cdaa5ff-0501-4d8f-9b14-d4ac1d40e524/

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.