Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
If the 'purely local + self-evolving profile' claims hold up, the project sits at an interesting intersection: personal-RAG-style memory plus autonomous multi-platform browsing.
Who should use it
Who should skip it
Pass on whiteguo233/OpenBiliClaw if your environment cannot support the access controls and sandboxing this risk profile requires.
About this signal
whiteguo233/OpenBiliClaw is tracked by RepoRadar as a developer tool in the Radar section. It was first seen on 2026-06-12 and last updated on 2026-06-12. The current verdict is 'watch' with a Silver tier and review needed setup difficulty. Across RepoRadar's eight signals, whiteguo233/OpenBiliClaw is strongest on practical usefulness (7.4) and open-source/build quality (7.4) and weakest on momentum (3.5) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed. 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 whiteguo233/OpenBiliClaw a composite score of 7.4 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 28.4 and never affects the composite score or tier. The risk label of 'high' 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
High risk: do not use without strong containment, approvals, and hands-on review.