Bifrost vs Instructor
Bifrost leads on trust: 90.3/100 (Grade A) against 70.2/100 (Grade B), a 20.1-point gap. Bifrost leads on supply-chain integrity and provenance; Instructor leads on adoption and rests on broader evidence. Note: Bifrost's evidence coverage is thinner (coverage B vs A) — its score rests on fewer independent signal types.
Open-source, high-performance AI gateway that works as your LLM gateway, MCP gateway and agent gateway. One OpenAI-compatible API for 10,000+ models, with failover, load balancing, semantic caching, virtual keys, budgets and MCP Code Mode. Works with any SDK or agent and adds under 200µs of…
Choose Bifrost if supply-chain integrity and provenance matter most.
- +9.5Safety / Integrity: OSSF Scorecard 7.3 against 5.7
- +7.2Identity / Provenance: package provenance attested, against none
- +1.4Transparency: OSSF Scorecard 7.3 against 5.7
structured outputs for llms
Choose Instructor if adoption matters most.
- +4.5Adoption: 2.6M weekly downloads against 2k
- A vs BEvidence coverage: 4 of 5 independent signal types, against 3
Where they differ
An independent, evidence-based trust comparison of Bifrost and Instructor, two LLM Gateways & Infra projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Full evidence
| Signal | Bifrostmaximhq/bifrost | Instructor567-labs/instructor |
|---|---|---|
| HVTrust score | 90.3 | 70.2 |
| Evidence grade | A | B |
| Coverage grade | B | A |
| Overall rank | #28 | #377 |
| Rank in LLM Gateways & Infra | #1 | #5 |
| GitHub stars | 9.9k | 14.1k |
| Last updated | today | 3d ago |
| Build provenance | Yes | No |
| OSSF Scorecard | 7.3 / 10 | 5.7 / 10 |
| License | Apache-2.0 | MIT |
| Downloads | 2k/wk | 2.6M/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 21.6 | 12.1 |
| Identity & provenance / 18 | 18.0 | 10.8 |
| Transparency / 17 | 14.7 | 13.3 |
| Maintenance / 20 | 20.0 | 19.8 |
| Adoption / 20 | 14.0 | 18.5 |
| Runtime capability surface (full matrix) | ||
| MCP server | Declared | — |
| External providers | — | 11 — Amazon Bedrock, Anthropic, Cohere, … |
| Requires API keys | No | Yes |
| Plugin surface | plugins | — |
| Provenance drift | Match | Unknown |
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.4 →