updated 2026-10-15 04:08 UTC

OpenBiliClaw

Repository Website

本地私有、开源的自进化跨平台 AI 内容发现 Agent：先理解你，再主动从 B站、小红书、抖音、YouTube、X、知乎、Reddit、微博等平台与开放 Web 寻找内容。（支持 deepseek harness 插件） | Local-first open-source cross-platform AI content discovery agent: understands you, then proactively finds content across Bilibili, Xiaohongshu, Douyin, YouTube, X, Zhihu, Reddit…

Agent Skills Python Listed MIT

Is OpenBiliClaw safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.4 / 10
Provenance None
Signed commits 15%
Last push today
Compare OpenBiliClaw

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: OpenBiliClaw scores 54.4/100 (Grade C), ranked #186 of 371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.4/10; 15% of recent commits are signed; last pushed 2026-10-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How OpenBiliClaw could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships OpenBiliClaw and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Partly signed

    github.com/whiteguo233/OpenBiliClaw, MIT, last pushed 2026-10-15. 15% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.4/10 (scanned Oct 13, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 7
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 1
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    No registry package. OpenBiliClaw is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-28 OSSF Scorecard: 3.5/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues OpenBiliClaw’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How OpenBiliClaw compares in Agent Skills

  1. #184 Claude Howto 54.5 +0.1
  2. #185 anti-slop 54.4 ±0
  3. #186 OpenBiliClaw 54.4 this agent
  4. #187 Han 54.3 −0.1
  5. #188 Cc Wf Studio 54.0 −0.4

Bars show each HVTrust score; the tick marks OpenBiliClaw’s 54.4.

Where the 54.4 comes from

HVTrust dimensions vs the Agent Skills average

54.4 / 100 · 100.0% confidence

OpenBiliClaw Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.0 / 25
3.0 below avg 8.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
11.4 / 17
0.7 below avg 12.1
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.9 above avg 14.1
AdoptionLog-scaled stars · package downloads
8.5 / 20
in line with avg 9.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-01
Rank Moved
Rank dropped 16 spots (#171 → #187)
2026-09-25
Grade Changed
Trust grade D → C
2026-09-25
Rank Moved
Rank rose 148 spots (#316 → #168)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.4/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for OpenBiliClaw View Agent Skills Report missing data
81.8
Activity sub-score · out of 100
#186
In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-15 04:08 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-15

Activity & Reach

Stars
3.4k
Forks
186
Last Push
2026-10-15
today
Commits (4 wk)
212
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
20
Rank Change
▲1
was #187

Analysis

Activity Inputs

81.8 / 100
StarsRepository reach
21.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
10.6 / 20

Common questions about OpenBiliClaw

Public trust evidence for OpenBiliClaw is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does OpenBiliClaw publish package provenance?
No published build provenance is currently detected for OpenBiliClaw. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does OpenBiliClaw have an OpenSSF Scorecard?
OpenBiliClaw has an OpenSSF Scorecard score of 3.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is OpenBiliClaw actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does OpenBiliClaw use?
OpenBiliClaw ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenBiliClaw's commits signed?
15% of the last 100 commits to OpenBiliClaw are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • browser
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to OpenBiliClaw's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI

Maintain OpenBiliClaw?

For maintainers

HVTrust scores OpenBiliClaw from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 11HVTrust 3Listed 2Scorecard 1Delisted 1Surface 1Grade 1
2026-10-01
Rank Moved
Rank dropped 16 spots (#171 → #187)
2026-09-25
Grade Changed
Trust grade D → C
2026-09-25
Rank Moved
Rank rose 148 spots (#316 → #168)
2026-09-25
HVTrust Changed
HVTrust up 18.7pts (36.0 → 54.7)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI
2026-09-23
Rank Moved
Rank dropped 49 spots (#266 → #315)
2026-09-23
HVTrust Changed
HVTrust up 4.9pts (31.1 → 36.0)
2026-09-22
Newly Listed
First tracked at rank #266
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-10
Rank Moved
Rank dropped 11 spots (#292 → #303)
2026-09-03
Rank Moved
Rank dropped 12 spots (#243 → #255)
2026-09-02
Rank Moved
Rank dropped 12 spots (#231 → #243)
2026-09-01
Rank Moved
Rank dropped 13 spots (#218 → #231)
2026-08-31
Rank Moved
Rank dropped 17 spots (#201 → #218)
2026-08-30
Rank Moved
Rank dropped 36 spots (#165 → #201)
2026-08-29
Rank Moved
Rank dropped 40 spots (#125 → #165)
2026-08-28
Scorecard Added
OSSF Scorecard: 3.5/10
2026-08-28
Rank Moved
Rank rose 149 spots (#274 → #125)
2026-08-28
HVTrust Changed
HVTrust up 17.8pts (18.1 → 35.9)
2026-08-26
Newly Listed
First tracked at rank #270
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.4 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/openbiliclaw.svg)](https://hvtracker.net/agents/openbiliclaw)
HTML:
<a href="https://hvtracker.net/agents/openbiliclaw"><img src="https://hvtracker.net/badge/openbiliclaw.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON