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.

WatchMeJoustMyFlags/JoustMania

https://github.com/WatchMeJoustMyFlags/JoustMania · scanned 2026-06-16 04:41 UTC (1 month, 2 weeks ago)

4 raw signals (0 security + 4 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 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.

JSON

55.6% cov · 4 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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 63.3/100 with 55.6% coverage. It contains 59 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 4 findings — concentrated in security (2), quality (2). Risk profile is high: 0 critical, 2 high, 2 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 4 of 4 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: .env

`.env` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.

.env ConfigEnv fileRuntime env

high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: .env.mock

`.env.mock` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.

.env.mock ConfigEnv fileRuntime env

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md

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.

CLAUDE.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.

Repo hardeningGenerated 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/f41bcb9e-5313-4e12-ae32-1e860db81580/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f41bcb9e-5313-4e12-ae32-1e860db81580/

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.