Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for creators and builders who want an agent-friendly way to move from a short brief to a tracked storyboard and generated assets inside one local workspace.
Who should use it
Who should skip it
Skip Yuuhann1999/codex-storyboard if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
Yuuhann1999/codex-storyboard is tracked by RepoRadar as a codex plugin in the AI Creative section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. The standout signals for Yuuhann1999/codex-storyboard are workflow potential (9.0) and open-source/build quality (8.4), while maturity (5.8) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned Yuuhann1999/codex-storyboard a composite score of 7.9 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It can trigger image and video generation tasks from a local workspace, so start with test provider keys and a small spend cap; Local project files and generated assets can accumulate quickly across multiple boards, so validate its folder and cleanup workflow before using it on client work.