How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-06 18:09 UTC·Repo last pushed 9 days ago
Activity & Reach
Stars
3.3k
Forks
441
Last Push
2026-05-28
9 days ago
Commits (4 wk)
8
Downloads (7d)
15,071
pypi
HN mentions (30d)
—
Open Issues
13
Rank Change
NEW
Analysis
HVTrust Dimensions
34.0 / 100 · 67.0% confidence
Safety / IntegrityOSSF, provenance, signatures
2.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
15.2 / 20
AdoptionStars and downloads
14.0 / 20
Activity Inputs
69.1 / 100
StarsRepository reach
21.1 / 30
FreshnessLast push recency
23.8 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
12.3 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
50%
of last 100 commits verified
Is BeeAI Framework safe?
Public trust evidence for BeeAI Framework 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 BeeAI Framework publish package provenance?
No published build provenance is currently detected for BeeAI Framework. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does BeeAI Framework have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for BeeAI Framework. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is BeeAI Framework actively maintained?
Maintained. Last push was 9 days ago.
What license does BeeAI Framework use?
BeeAI Framework ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are BeeAI Framework's commits signed?
50% of the last 100 commits to BeeAI Framework 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.
Runtime trust
HVTrust currently does not score runtime-trust fields yet. This public view shows a compact runtime snapshot from repo docs and manifests. An experimental ranking preview is available in Score Lab →, and progress is tracked on the roadmap →
MCP Server Support
high confidence
Implemented
BeeAI Framework appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
5 detected
Public provider/service dependencies detected.
Amazon Bedrock
Anthropic
OpenAI
Postgres
Qdrant
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
code
database
search
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
MCP support live
External deps live
Tool / plugin surface live
Package provenance drift live
Maintain BeeAI Framework?
HVTrust scores BeeAI Framework 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.
