BotSharp

AI Multi-Agent Framework in .NET

Agent Frameworks C# Grade C Listed Apache-2.0
58.3/100
Rank #343 of 1204
Compare BotSharp

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-08-05 · 4d ago
Recent change
Rank +1

Is BotSharp safe? BotSharp scores 58.3/100 (Grade C), ranked #343 of 1204 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 5.2/10; 28% of recent commits are signed; last pushed 2026-08-05. 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-08-08
Rank Moved
Rank dropped 87 spots (#255 → #342)
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini, OpenAI, Qdrant
2026-07-14
Rank Moved
Rank dropped 14 spots (#229 → #243)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.2/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.
80.0
Activity sub-score · out of 100
#51

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-08-09 20:01 UTC · Repo last pushed 4 days ago

Activity & Reach

Stars
3.1k
Forks
643
Last Push
2026-08-05
4 days ago
Commits (4 wk)
53
Downloads (7d)
HN mentions (30d)
Open Issues
43
Rank Change
▼1
was #342

Analysis

HVTrust Dimensions vs Agent Frameworks

58.3 / 100 · 100.0% confidence

BotSharp Agent Frameworks average (117 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.9 / 25
in line with avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
12.9 / 17
1.3 above avg 11.6
Maintenance60% last-push freshness · 40% commit activity
18.6 / 20
4.3 above avg 14.3
AdoptionLog-scaled stars · package downloads
8.4 / 20
3.0 below avg 11.4

Activity Inputs

80.0 / 100
StarsRepository reach
20.9 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
21.6 / 25
CommunityFork signal
13.1 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.2 / 10
OpenSSF Scorecard · scanned Aug 9, 2026
Signed Commits
28%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 9
CII-Best-Practices 0
Code-Review 1
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 10

Is BotSharp safe?

BotSharp 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 BotSharp publish package provenance?
No published build provenance is currently detected for BotSharp. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does BotSharp have an OpenSSF Scorecard?
BotSharp has an OpenSSF Scorecard score of 5.2/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 BotSharp actively maintained?
Actively maintained. The repository was pushed to within the last 4 day(s).
What license does BotSharp use?
BotSharp ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are BotSharp's commits signed?
28% of the last 100 commits to BotSharp 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
Declared
Declared 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
How this surface has changed

Detected changes to BotSharp'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-08-07
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini, OpenAI, Qdrant

Maintain BotSharp?

For maintainers

HVTrust scores BotSharp 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 5Listed 1Score 1HVTrust 1Grade 1Scorecard 1Surface 1
2026-08-08
Rank Moved
Rank dropped 87 spots (#255 → #342)
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini, OpenAI, Qdrant
2026-07-14
Rank Moved
Rank dropped 14 spots (#229 → #243)
2026-07-13
Rank Moved
Rank dropped 29 spots (#200 → #229)
2026-06-24
Scorecard Added
OSSF Scorecard: 5.5/10
2026-06-24
Grade Changed
Trust grade D → C
2026-06-24
Rank Moved
Rank rose 108 spots (#287 → #179)
2026-06-24
HVTrust Changed
HVTrust up 35.8pts (23.8 → 59.6)
2026-06-23
Rank Moved
Rank dropped 12 spots (#275 → #287)
2026-06-23
Activity Score Changed
Activity score up 7pts (72 → 79)
2026-06-21
Newly Listed
First tracked at rank #272

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 58.3 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/botsharp.svg)](https://hvtracker.net/agents/botsharp)
HTML:
<a href="https://hvtracker.net/agents/botsharp"><img src="https://hvtracker.net/badge/botsharp.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.2 · Raw JSON