BitFun

OpenBitFun combines a high-performance agent runtime written in Rust with a polished desktop application. It pairs the d

Agent Frameworks Rust Grade C Listed MIT
57.5/100
Rank #688 of 1328
Compare BitFun

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-18 · 0d ago
Recent change
Rank +1

Is BitFun safe? BitFun scores 57.5/100 (Grade C), ranked #688 of 1328 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 4.5/10; 26% of recent commits are signed; last pushed 2026-09-18. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-15
Rank Moved
Rank dropped 35 spots (#655 → #690)
2026-09-12
Rank Moved
Rank rose 18 spots (#678 → #660)
2026-09-10
Rank Moved
Rank dropped 17 spots (#659 → #676)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.5/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.
81.2
Activity sub-score · out of 100
#66

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-09-18 13:03 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-18

Activity & Reach

Stars
2.3k
Forks
234
Last Push
2026-09-18
today
Commits (4 wk)
1623
Downloads (7d)
HN mentions (30d)
Open Issues
48
Rank Change
▲4
was #692

Analysis

HVTrust Dimensions vs Agent Frameworks

57.5 / 100 · 100.0% confidence

BitFun Agent Frameworks average (122 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.9 / 25
2.8 below avg 9.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
12.3 / 17
in line with avg 12.4
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.1 above avg 13.9
AdoptionLog-scaled stars · package downloads
8.1 / 20
3.1 below avg 11.2

Activity Inputs

81.2 / 100
StarsRepository reach
20.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
11.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.5 / 10
OpenSSF Scorecard · scanned Sep 15, 2026
Signed Commits
26%
of last 100 commits verified
Binary-Artifacts 8
Branch-Protection 3
CI-Tests 10
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 0
SAST 0
Security-Policy 10
Signed-Releases 8
Token-Permissions 0
Vulnerabilities 0

Is BitFun safe?

BitFun has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does BitFun publish package provenance?
No published build provenance is currently detected for BitFun. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does BitFun have an OpenSSF Scorecard?
BitFun has an OpenSSF Scorecard score of 4.5/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 BitFun actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does BitFun use?
BitFun ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are BitFun's commits signed?
26% of the last 100 commits to BitFun 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
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

Maintain BitFun?

For maintainers

HVTrust scores BitFun 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.

Reputation Timeline

Signal history
Rank 19Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-15
Rank Moved
Rank dropped 35 spots (#655 → #690)
2026-09-12
Rank Moved
Rank rose 18 spots (#678 → #660)
2026-09-10
Rank Moved
Rank dropped 17 spots (#659 → #676)
2026-09-08
Rank Moved
Rank rose 22 spots (#675 → #653)
2026-09-07
Rank Moved
Rank dropped 41 spots (#634 → #675)
2026-09-05
Rank Moved
Rank dropped 68 spots (#557 → #625)
2026-09-04
Rank Moved
Rank dropped 14 spots (#543 → #557)
2026-09-03
Rank Moved
Rank dropped 23 spots (#520 → #543)
2026-09-02
Rank Moved
Rank dropped 23 spots (#497 → #520)
2026-09-01
Rank Moved
Rank dropped 13 spots (#484 → #497)
2026-08-31
Rank Moved
Rank dropped 29 spots (#455 → #484)
2026-08-30
Rank Moved
Rank rose 13 spots (#468 → #455)
2026-08-29
Rank Moved
Rank dropped 14 spots (#454 → #468)
2026-08-27
Scorecard Added
OSSF Scorecard: 4.2/10
2026-08-27
Grade Changed
Trust grade D → C
2026-08-27
Rank Moved
Rank rose 548 spots (#994 → #446)
2026-08-27
HVTrust Changed
HVTrust up 33.1pts (23.5 → 56.6)
2026-08-26
Rank Moved
Rank dropped 92 spots (#902 → #994)
2026-08-24
Rank Moved
Rank dropped 12 spots (#890 → #902)
2026-08-16
Rank Moved
Rank dropped 19 spots (#891 → #910)
2026-08-10
Rank Moved
Rank dropped 52 spots (#838 → #890)
2026-08-08
Rank Moved
Rank dropped 372 spots (#461 → #833)
2026-08-03
Newly Listed
First tracked at rank #438

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

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.3 · Raw JSON