updated 2026-09-08 14:33 UTC

BISHENG

dataelement/bisheng

BISHENG is an open LLM devops platform for next generation Enterprise AI applications. Powerful and comprehensive featur

Workflow Platforms Python Grade D Listed Apache-2.0
20.7/100
Rank #1315 of 1328
Compare BISHENG

How does it stack up against its Workflow Platforms neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-09-08 · 0d ago
Recent change
New

Is BISHENG safe? BISHENG scores 20.7/100 (Grade D), ranked #1315 of 1328 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 1% of recent commits are signed; last pushed 2026-09-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Workflow Platforms

#21 Julep — 46.9 (D) → #22 LiteFlow — 43.4 (D) → #23 PromptFlow — 41.7 (D) → #24 Activepieces — 41.1 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-08
Newly Listed
First tracked at rank #1315
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 BISHENG View Workflow Platforms Report missing data
89.8
Activity sub-score · out of 100
#25
In Workflow Platforms

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. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-08 14:33 UTC · Repo last pushed today

Activity & Reach

Stars
11.9k
Forks
2.0k
Last Push
2026-09-08
today
Commits (4 wk)
263
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
113
Rank Change
NEW

Analysis

HVTrust Dimensions vs Workflow Platforms

20.7 / 100 · 50.0% confidence

BISHENG Workflow Platforms average (25 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.1 / 25
10.0 below avg 10.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.9 below avg 12.4
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
2.3 above avg 17.7
AdoptionLog-scaled stars · package downloads
9.8 / 20
2.9 below avg 12.7

Activity Inputs

89.8 / 100
StarsRepository reach
24.5 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
1%
of last 100 commits verified

Is BISHENG safe?

Public trust evidence for BISHENG 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 BISHENG publish package provenance?
No published build provenance is currently detected for BISHENG. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does BISHENG have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for BISHENG. 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 BISHENG actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does BISHENG use?
BISHENG ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are BISHENG's commits signed?
1% of the last 100 commits to BISHENG 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
7 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • browser
  • database
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 BISHENG?

For maintainers

HVTrust scores BISHENG 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
Listed 1
2026-09-08
Newly Listed
First tracked at rank #1315
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Workflow Platforms

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