Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Most AI researchers + video-editing model developers + visual-effects studio engineers today have built video-editing evaluation workflows that require stitching together a hand-curated annotated example set (thousands of video edits + ground-truth scores) + a hand-built VLM-based reward model (per-dimension scoring + composite metric + cross-dimension calibration) + a hand-curated live leaderboar
Who should use it
Who should skip it
Move on from Visko-Platform/VEFX-Bench if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
Visko-Platform/VEFX-Bench is tracked by RepoRadar as a tool in the Radar section. It was first seen on 2026-07-09 and last updated on 2026-07-09. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, Visko-Platform/VEFX-Bench is strongest on momentum (9.0) and workflow potential (8.5) and weakest on maturity (5.7) — a profile worth weighing against your own priorities. 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 Visko-Platform/VEFX-Bench a composite score of 7.8 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 0.0 and never affects the composite score or tier. The risk label of 'none' 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
The 208* repo is at solid active maintenance (created 2026-05-16; Apache-2.0 verified on 2026-07-09) and the consumer SHOULD note that the 32B reward model variant requires significant VRAM (significantly more than the 4B variant); the consumer SHOULD pin the dataset + reward model tags rather than relying on `:latest` for production; the consumer SHOULD follow the official submission process to the live leaderboard at https://vefx-leaderboard.com to ensure their results are tracked correctly.