Repo brief: RayWangQvQ/BiliBiliToolPro

Generated by RepoPilot · document generated 2026-09-13 · concise human review Evidence snapshot · analyzed 2026-09-13T20:02:07.649Z · commit d552d69817cf

Verdict

Mixed — Single-maintainer risk — review before adopting

• Last commit 2d ago
• 2 active contributors
• GPL-3.0 licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

BiliBiliToolPro is a C# (.NET) automation framework that performs daily tasks on Bilibili (China's premier video platform), including auto-login via QR code, daily experience farming (watch/coin/share/like), live stream AFK farming, manga/live check-ins, monthly pass perks collection, and B-coin charging. It supports multi-account execution across Docker, Kubernetes, Qinglong (a Chinese task scheduler), and standalone deployment with push notifications to Telegram, WeChat, DingTalk, PushPlus, and custom webhooks. Monorepo structure: Ray.BiliBiliTool.sln (C# solution root) with core library handling Bilibili API calls and task orchestration; bruno/ directory contains API request definitions…

Start here

Open these first:

• Ray.BiliBiliTool.sln — Root solution file that defines the entire .NET project structure and all dependencies for the BiliBili automation tool
• Dockerfile — Container definition required to understand how the tool is packaged and deployed across Docker, K8s, and serverless…
• .github/workflows/publish-image.yml — CI/CD pipeline that orchestrates multi-architecture builds and releases; critical for understanding deployment automation
• common.props — Centralized NuGet package and build configuration shared across all projects; defines dependency versions and compilation…
• Directory.Packages.props — Central package management file using NuGet Central Package Management; controls all transitive dependency versions

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone and build:

git clone https://github.com/RayWangQvQ/BiliBiliToolPro.git
cd BiliBiliToolPro
dotnet restore Ray.BiliBiliTool.sln
dotnet build Ray.BiliBiliTool.sln

Or deploy via Docker (Dockerfile present):

docker build -t bilitool .
docker run -e "ACCOUNT=<account>" -e "PASSWORD=<password>" bilitool

For Kubernetes: use .github/workflows/ as reference or see Chart deployment method (1.1.5).

Daily commands:

Dev build & test:

dotnet restore
dotnet build
dotnet test  # if test projects exist in .sln

Run locally:

…shortened for this brief.

Key cautions & unknowns

• Small team — 2 contributors active in recent commits
• Single-maintainer risk — top contributor 99% of recent commits
• GPL-3.0 is copyleft — check downstream compatibility
• Bilibili API brittleness: API endpoints change frequently (evidenced by multiple vip_center versions in bruno/); no SDK available, so wrapper breaks silently on API changes. WBI signature: Bilibili uses a Web…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.