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.

digitalentity/replistore

https://github.com/digitalentity/replistore · scanned 2026-06-17 01:56 UTC (1 month, 1 week ago)

5 raw signals (0 security + 5 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -5.5 (diff) · 5 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:56
Diff: previous → latest scan
Score Δ
-5.50
Gaps added
5
Gaps resolved
0
Edges changed
+62 / -0
New gaps in latest scan:
  • Privileged port 50 in use medium
  • Very large file: internal/fuse/fs_test.go (1706 lines) low
  • Placeholder or mock-heavy implementation detected medium
  • Critical user flow still appears backed by mock or placeholder data medium
  • Agent instructions exist but release-hardening basics are missing medium
v#IDStatusScoreGapsNodesCommitStarted
v scan_3ffd7b143992 ok 71.2 5 81 Jun 17 01:56
v scan_36db57d55a2f 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/ca9181d2-9b61-4172-b919-93e66755eaea/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ca9181d2-9b61-4172-b919-93e66755eaea/

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.