Is Budibase safe to use?

Budibase has an HVTrust score of 63.6/100 (Grade C), ranked #268 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Budibase?

Budibase scores 63.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 28.2k GitHub stars and is categorized under Workflow Platforms.

Budibase

Budibase/budibase

AI agents, automations and apps that run your operations. Model agnostic.

Workflow Platforms TypeScript Grade C Listed NOASSERTION Source-available

63.6/100

Rank #268 of 1308

Compare Budibase

How does it stack up against its Workflow Platforms 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-18 · 1d ago

Recent change

Rank +4

Is Budibase safe? Budibase scores 63.6/100 (Grade C), ranked #268 of 1308 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.5/10; 48% of recent commits are signed; last pushed 2026-08-18. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Workflow Platforms

#11 Sim — 65.3 (B) → #12 Conductor — 65.1 (B) → #14 InsForge — 61.8 (C) → #15 Astron Agent — 57.3 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-19

Rank Moved

Rank dropped 14 spots (#254 → #268)

2026-08-14

Rank Moved

Rank rose 19 spots (#274 → #255)

2026-08-13

Rank Moved

Rank dropped 29 spots (#245 → #274)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.5/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.

Compare with another agent Get email alerts for Budibase View Workflow Platforms Report missing data

92.2

Activity sub-score · out of 100

#13

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 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 →

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

28.2k

Forks

2.2k

Last Push

2026-08-18

yesterday

Commits (4 wk)

1025

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

251

Rank Change

▼14

was #254

Analysis

HVTrust Dimensions vs Workflow Platforms

63.6 / 100 · 100.0% confidence

Budibase Workflow Platforms average (24 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

9.3 / 25

1.1 below avg 10.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

13.2 / 17

0.8 above avg 12.4

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

1.4 above avg 18.5

AdoptionLog-scaled stars · package downloads

10.7 / 20

2.2 below avg 12.9

Activity Inputs

92.2 / 100

StarsRepository reach

26.7 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

15.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.5 / 10

OpenSSF Scorecard · scanned Aug 18, 2026

Signed Commits

48%

of last 100 commits verified

Binary-Artifacts 6

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 2

Code-Review 8

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 9

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Budibase safe?

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Budibase may have internal security practices not visible through public signals.

Budibase 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 Budibase publish package provenance?

No published build provenance is currently detected for Budibase. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Budibase have an OpenSSF Scorecard?

Budibase has an OpenSSF Scorecard score of 5.5/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 Budibase actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Budibase use?

Budibase ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Budibase's commits signed?

48% of the last 100 commits to Budibase 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

medium confidence

1 detected

Public provider/service dependencies detected.

OpenAI

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

medium 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 Budibase'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-12

Provider Removed

Runtime surface shrank — no longer detected: Multi-provider (LiteLLM)

2026-07-17

Provider Added

Runtime surface grew — new detected provider dependency: Multi-provider (LiteLLM)

2026-06-01

Activity Resumed

Activity resumed

Maintain Budibase?

For maintainers

HVTrust scores Budibase 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

2026-08-19

Rank Moved

Rank dropped 14 spots (#254 → #268)

2026-08-14

Rank Moved

Rank rose 19 spots (#274 → #255)

2026-08-13

Rank Moved

Rank dropped 29 spots (#245 → #274)

2026-08-12

Provider Removed

Runtime surface shrank — no longer detected: Multi-provider (LiteLLM)

2026-08-12

Rank Moved

Rank rose 27 spots (#272 → #245)

2026-08-10

Rank Moved

Rank dropped 18 spots (#254 → #272)

2026-08-08

Rank Moved

Rank dropped 52 spots (#194 → #246)

2026-07-27

License Changed

License classification changed from open to source-available

2026-07-17

Provider Added

Runtime surface grew — new detected provider dependency: Multi-provider (LiteLLM)

2026-07-14

Rank Moved

Rank dropped 16 spots (#148 → #164)

2026-07-13

Rank Moved

Rank dropped 16 spots (#132 → #148)

2026-07-03

Grade Changed

Trust grade C → B

2026-07-01

Rank Moved

Rank rose 14 spots (#150 → #136)

2026-06-30

Rank Moved

Rank dropped 11 spots (#139 → #150)

2026-06-10

Rank Moved

Rank dropped 11 spots (#105 → #116)

2026-06-01

Scorecard Added

OSSF Scorecard: 5.2/10

2026-06-01

Activity Resumed

Activity resumed

2026-06-01

Grade Changed

Trust grade D → C

2026-06-01

Rank Moved

Rank rose 96 spots (#184 → #88)

2026-06-01

HVTrust Changed

HVTrust up 63.1pts (0.0 → 63.1)

2026-06-01

Activity Score Changed

Activity score up 92pts (0 → 92)

2026-05-31

Newly Listed

First tracked at rank #184

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/budibase.svg)](https://hvtracker.net/agents/budibase)
            
HTML:
            <a href="https://hvtracker.net/agents/budibase"><img src="https://hvtracker.net/badge/budibase.svg" alt="HVTrust"></a>

Other agents in Workflow Platforms

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.3 · Raw JSON