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.

kingdame/DwellTyme

https://github.com/kingdame/DwellTyme · scanned 2026-06-16 04:30 UTC (2 months ago)

13 raw signals (0 security + 13 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months ago · v1 · 9 actionable findings from 1 signal source. 4 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

66.7% cov · 9 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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

Showing 7 of 9 actionable findings. 13 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 5 occurrences Possible secret in .env.example

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

lines 2, 3, 4, 6, 9

.env.example:2, 3, 4, 6, 9 (5 hits)

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

`.env.schema` looks like a runtime dotenv file. It contains secret-looking assignments for CLOUDFLARE_R2_ACCESS_KEY_ID. Move real values to a secret manager and keep only `.env.example` style templates in source control.

.env.schema ConfigEnv fileRuntime env

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .windsurfrules

Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.

.windsurfrules:47 SecretsAgent instruction

medium System graph security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: .windsurfrules

Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.

.windsurfrules:18 Supply chainAgent 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, tests. 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

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 4 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

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/be7237cd-db5d-4ad8-9bdb-b8169addd275/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/be7237cd-db5d-4ad8-9bdb-b8169addd275/

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.