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.

dmitrat/WitDatabase

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

30 raw signals (0 security + 30 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -15.3 (diff) · 10 actionable findings from 1 signal source. 20 repeated signals grouped for readability. 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
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 61.4/100 with 55.6% coverage. It contains 1277 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 30 findings — concentrated in cicd (24), quality (5), security (1). Risk profile is high: 1 critical, 0 high, 8 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 10 of 10 actionable findings. 30 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.

critical System graph security Secrets conf 1.00 Possible secret in Sources/Core/OutWit.Database.Core.BouncyCastle/README.md
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
Sources/Core/OutWit.Database.Core.BouncyCastle/README.md:104
medium System graph quality Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
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 cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
softprops/action-gh-release@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/release.yml:216 CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/publish.yml CI/CD securitySupply chainGithub actions
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 27 placeholder/mock markers across 18 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 2 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph cicd CI/CD security conf 1.00 21 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-java@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
5 files, 21 locations
.github/workflows/release.yml:119, 125, 130, 180, 197 (5 hits)
.github/workflows/ci.yml:25, 31, 38, 59 (4 hits)
.github/workflows/pack.yml:32, 38, 45, 84 (4 hits)
.github/workflows/publish.yml:44, 50, 57, 135 (4 hits)
.github/workflows/test-one.yml:51, 57, 64, 102 (4 hits)
CI/CD securitySupply chainGithub actions
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/7c3aea83-22a1-41c4-b47b-8be404dcb514/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7c3aea83-22a1-41c4-b47b-8be404dcb514/

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.