updated 2026-08-06 05:00 UTC

Convex Chef

get-convex/chef

The only AI app builder that knows backend

UI & App Builders TypeScript Grade D Listed Apache-2.0
48.7/100
Rank #323 of 468
Compare Convex Chef

How does it stack up against its UI & App Builders 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 C · 2/5 signals
Last push
2026-07-16 · 21d ago
Recent change
No recent signal change

Is Convex Chef safe? Convex Chef scores 48.7/100 (Grade D), ranked #323 of 468 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.0/10; 100% of recent commits are signed; last pushed 2026-07-16. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in UI & App Builders

#11 Yao — 53.5 (C) → #12 Srcbook — 51.2 (C) → #13 CopilotKit — 49.9 (D) → #15 Bolt — 28.7 (D) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-29
Rank Moved
Rank dropped 10 spots (#311 → #321)
2026-07-19
Grade Changed
Trust grade C → D
2026-07-16
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.0/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.
Compare with another agent Get email alerts for Convex Chef View UI & App Builders Report missing data
58.0
Activity sub-score · out of 100
#14
In UI & App Builders

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 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-06 05:00 UTC · Repo last pushed 21 days ago

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
4.6k
Forks
927
Last Push
2026-07-16
21 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
22
Rank Change
=
was #323

Analysis

HVTrust Dimensions vs UI & App Builders

48.7 / 100 · 100.0% confidence

Convex Chef UI & App Builders average (15 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.0 / 25
1.4 below avg 11.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.9 below avg 12.7
Transparency50% declared license · 50% OSSF Scorecard
11.9 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
10.6 / 20
6.4 below avg 17.0
AdoptionLog-scaled stars · package downloads
8.8 / 20
4.2 below avg 13.0

Activity Inputs

58.0 / 100
StarsRepository reach
22.0 / 30
FreshnessLast push recency
22.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.8 / 20

Supply Chain Trust

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

Is Convex Chef safe?

Public trust evidence for Convex Chef 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 Convex Chef publish package provenance?
No published build provenance is currently detected for Convex Chef. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Convex Chef have an OpenSSF Scorecard?
Convex Chef has an OpenSSF Scorecard score of 4.0/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 Convex Chef actively maintained?
Maintained. Last push was 21 days ago.
What license does Convex Chef use?
Convex Chef ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Convex Chef's commits signed?
100% of the last 100 commits to Convex Chef 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
4 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
3 tags
Broad capability areas detected.
  • browser
  • code
  • shell
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 Convex Chef?

For maintainers

HVTrust scores Convex Chef 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
Rank 8HVTrust 2Grade 2Listed 1Scorecard 1Score 1
2026-07-29
Rank Moved
Rank dropped 10 spots (#311 → #321)
2026-07-19
Grade Changed
Trust grade C → D
2026-07-16
Grade Changed
Trust grade D → C
2026-07-16
Rank Moved
Rank rose 37 spots (#337 → #300)
2026-07-16
HVTrust Changed
HVTrust up 5.6pts (44.5 → 50.1)
2026-07-16
Activity Score Changed
Activity score up 12pts (49 → 61)
2026-07-15
Rank Moved
Rank dropped 25 spots (#312 → #337)
2026-07-14
Rank Moved
Rank dropped 18 spots (#294 → #312)
2026-07-13
Rank Moved
Rank dropped 34 spots (#260 → #294)
2026-06-24
Rank Moved
Rank dropped 33 spots (#204 → #237)
2026-06-23
Scorecard Added
OSSF Scorecard: 4.0/10
2026-06-23
Rank Moved
Rank rose 85 spots (#289 → #204)
2026-06-23
HVTrust Changed
HVTrust up 28.9pts (20.5 → 49.4)
2026-06-21
Rank Moved
Rank dropped 30 spots (#257 → #287)
2026-06-20
Newly Listed
First tracked at rank #257
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in UI & App Builders

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