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.

declaw-ai/.github

https://github.com/declaw-ai/.github · scanned 2026-06-17 01:54 UTC (1 month, 1 week ago)

1 raw signals (0 security + 1 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -7.9 (diff) · 1 actionable finding from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

22.2% cov · 1 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 1 Low 0 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1 Crowd 0 Layer: Security 1

Exclude dismissed / FP Exclude test files

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

Jun 16 03:57

Jun 17 01:54

Diff: previous → latest scan

Score Δ

-7.90

Gaps added

Gaps resolved

Edges changed

+2 / -0

New gaps in latest scan:

No auth library detected medium

v#	ID	Status	Score	Gaps	Nodes	Commit	Started
v	`scan_eba222e717dd`	ok	68.8	1	3	—	Jun 17 01:54
v	`scan_ae0697aaee27`	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/baf55d43-296a-4a8c-a52e-458419057772/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/baf55d43-296a-4a8c-a52e-458419057772/

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.