Is Tambo safe to use?

Tambo has an HVTrust score of 83.6/100 (Grade A), ranked #58 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Tambo?

Tambo scores 83.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 11.2k GitHub stars and is categorized under UI & App Builders.

Tambo

tambo-ai/tambo

Generative UI SDK for React

UI & App Builders TypeScript Grade A Listed MIT

83.6/100

Rank #58 of 1283

Compare Tambo

How does it stack up against its UI & App Builders neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-11 · 0d ago

Recent change

No recent signal change

Is Tambo safe? Tambo scores 83.6/100 (Grade A), ranked #58 of 1283 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.3/10; 100% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in UI & App Builders

#1 Neo — 88.1 (A) → #2 OpenUI — 86.8 (A) → #4 Open WebUI — 83.4 (A) → #5 LibreChat — 74.2 (B) →

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-07-28

Newly Listed

First tracked at rank #49

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.3/10. Tighten the weakest checks to improve public safety evidence.

Compare with Neo Get email alerts for Tambo View UI & App Builders Report missing data

77.1

Activity sub-score · out of 100

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 A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Activity & Reach

Stars

11.2k

Forks

562

Last Push

2026-08-11

today

Commits (4 wk)

Downloads (7d)

6,469

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #57

Analysis

HVTrust Dimensions vs UI & App Builders

83.6 / 100 · 100.0% confidence

Tambo UI & App Builders average (17 agents)

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

19.1 / 25

9.0 above avg 10.1

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.5 above avg 12.5

Transparency50% declared license · 50% OSSF Scorecard

13.0 / 17

1.1 above avg 11.9

Maintenance60% last-push freshness · 40% commit activity

16.8 / 20

0.7 above avg 16.1

AdoptionLog-scaled stars · package downloads

14.8 / 20

2.4 above avg 12.4

Activity Inputs

77.1 / 100

StarsRepository reach

24.3 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

15.0 / 25

CommunityFork signal

12.8 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.3 / 10

OpenSSF Scorecard · scanned Aug 10, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 10

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Tambo safe?

Public supply-chain signals for Tambo are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Tambo carries less obvious unverified-evidence risk than projects with thin signals.

Does Tambo publish package provenance?

Yes. Tambo's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Tambo have an OpenSSF Scorecard?

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

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

What license does Tambo use?

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

Are Tambo's commits signed?

100% of the last 100 commits to Tambo 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.

Compare Tambo head-to-head

Tambo vs Neo → Tambo vs OpenUI → Tambo vs Open WebUI →

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

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

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 signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Tambo?

For maintainers

HVTrust scores Tambo 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-07-28

Newly Listed

First tracked at rank #49

GitHub → npm: @tambo-ai/react

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in UI & App Builders

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