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.

bedardandy/maine-court-forms

https://github.com/bedardandy/maine-court-forms · scanned 2026-06-17 01:41 UTC (1 month, 2 weeks ago)

58 raw signals (0 security + 58 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ +18.5 (diff) · 57 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

55.6% cov · 57 findings

Severity distribution — click a segment to filter

Active filters: severity: medium × excluding tests × Reset all

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

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 95.2/100 with 55.6% coverage. It contains 4171 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 58 findings — concentrated in quality (50), software (7), cicd (1). Risk profile is low: 0 critical, 0 high, 6 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 6 of 57 actionable findings. 58 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .mcp.json

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.mcp.json VerificationMcp config

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: forms/CR-112/SKILL.md

forms/CR-112/SKILL.md VerificationSkill file

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: forms/CV-183/SKILL.md

forms/CV-183/SKILL.md VerificationSkill file

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — tools/smoke_fact_patterns.py:344

`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 14 placeholder/mock markers across 9 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

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/6d2e005f-3ad6-477f-9f4d-aeb557f7ac4a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6d2e005f-3ad6-477f-9f4d-aeb557f7ac4a/

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.