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.
Sign up free Scan another repo

yukimemi/kanade

https://github.com/yukimemi/kanade · scanned 2026-06-16 01:09 UTC (2 months, 1 week ago)

116 raw signals (51 security + 65 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
71.0
/100
Security checks
71
7 findings
System graph
71
88.9% cov · 53 findings
Critical
2
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 3 Medium 11 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 53 Crowd 0 Layer: Quality 49 Security 2 Frontend 5 Network 1 Cicd 3
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 71.0/100 with 88.9% coverage. It contains 937 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 65 findings — concentrated in quality (46), cicd (12), frontend (5). Risk profile is low: 0 critical, 0 high, 19 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 24 of 60 actionable findings. 252 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 Security checks quality Practices conf 0.82 14 occurrences Foundry mined mock as real or placeholder: yukimemi/kanade
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
14 occurrences
repo-level (14 hits)
critical Security checks security auth conf 0.78 12 occurrences Foundry mined security auth guardrail gaps: yukimemi/kanade
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
12 occurrences
repo-level (12 hits)
high Security checks quality Practices conf 0.84 9 occurrences Foundry mined bad chains: yukimemi/kanade
Comment chain pattern product: bad_chains Repo: yukimemi/kanade Thread: yukimemi/kanade#96 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_has_verif…
9 occurrences
repo-level (9 hits)
high Security checks quality Quality conf 0.76 34 occurrences Foundry mined schema ui api mismatch: yukimemi/kanade
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: supported_by_verification_signal Repo…
34 occurrences
repo-level (34 hits)
high Security checks quality Testing conf 0.78 23 occurrences Foundry mined test ci gap after feedback: yukimemi/kanade
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_verificati…
23 occurrences
repo-level (23 hits)
medium Security checks quality Practices conf 0.62 73 occurrences Foundry mined assumption checks: yukimemi/kanade
Comment chain pattern product: assumption_checks Repo: yukimemi/kanade Thread: yukimemi/kanade#98 Outcome: ambiguous_needs_more_evidence Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_h…
73 occurrences
repo-level (73 hits)
medium Security checks quality Practices conf 0.70 22 occurrences Foundry mined unresolved feedback: yukimemi/kanade
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: supp…
22 occurrences
repo-level (22 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — crates/kanade-backend/web/src/lib/api.ts:50
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
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 4 occurrences Frontend route `/agents/:pcId` has no Link/navigate to it — crates/kanade-backend/web/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
4 occurrences
repo-level (4 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
peter-evans/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 2 locations
.github/workflows/apm-bump.yml:115
.github/workflows/kata-apply.yml:83
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 7 occurrences 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.
7 files, 7 locations
.github/workflows/apm-bump.yml
.github/workflows/auto-tag.yml
.github/workflows/claude-review.yml
.github/workflows/claude.yml
.github/workflows/docs.yml
.github/workflows/kata-apply.yml
.github/workflows/release.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in crates/kanade-client/web/src/main.ts:298
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
crates/kanade-client/web/src/main.ts:298 Direct innerhtml assignment
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 108 placeholder/mock markers across 34 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 network Security conf 1.00 Privileged port 11 in use
Port 11 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
configs/schedules/morning-greeting.yaml Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
3 test file(s) for 233 source file(s) (ratio 0.01). Consider adding integration or unit tests for critical paths.
Coverage
low System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 3 locations
.github/workflows/docs.yml:84, 99 (2 hits)
.github/workflows/auto-tag.yml:50
CI/CD securitySupply chainGithub actions
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph quality Complexity conf 1.00 Very large file: crates/kanade-agent/src/local_scheduler.rs (2179 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/kanade-backend/src/api/schedules.rs (1609 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/kanade-backend/src/projector/results.rs (1259 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/kanade-backend/src/scheduler/mod.rs (1310 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/kanade-shared/src/manifest.rs (5397 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/4d2efe92-8b39-40db-ab05-9024fc62dd48/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/4d2efe92-8b39-40db-ab05-9024fc62dd48/

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.