Is Tambo safe to use?

Tambo has an HVTrust score of 79.8/100 (Grade B), ranked #171 of 1378 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 79.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 11.2k GitHub stars and is categorized under UI & App Builders.

Tambo

Repository

Website

Generative UI SDK for React

UI & App Builders TypeScript Listed MIT

Is Tambo safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 4.7 / 10

Provenance Attested

Signed commits 100%

Last push today

Advisories None known

Compare Tambo

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

Pick any agent to compare →

Suggest a correction

In detail: Tambo scores 79.8/100 (Grade B), ranked #171 of 1378 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 4.7/10; 100% of recent commits are signed; no published advisory affects its latest release (@tambo-ai/react); last pushed 2026-10-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How Tambo could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 4.7 to 9.0lowest checks: CII-Best-Practices 0, Dangerous-Workflow 0, Fuzzing 0 +7.7 → 87.5 A · #3 of 18

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Tambo and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/tambo-ai/tambo, MIT, last pushed 2026-10-21. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.7/10 (scanned Oct 17, 2026). The checks that decide who can get a change released:
- Code Review5
- Branch Protection4
- Signed Releasesn/a
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies2
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 7

CII-Best-Practices 0

Code-Review 5

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 7

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages Linked and attested
- npm @tambo-ai/react Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: @tambo-ai/react 1.4.0. No published advisory affects it (OSV, checked 2026-10-21).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Tambo.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Tambo’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Tambo compares in UI & App Builders

Bars show each HVTrust score; the tick marks Tambo’s 79.8.

Where the 79.8 comes from

HVTrust dimensions vs the UI & App Builders average

79.8 / 100 · 100.0% confidence

Tambo UI & App Builders average (18 agents)

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

18.4 / 25

7.3 above avg 11.1

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.2 above avg 12.8

Transparency50% declared license · 50% OSSF Scorecard

12.5 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.9 / 20

1.7 below avg 15.6

AdoptionLog-scaled stars · package downloads

14.8 / 20

2.5 above avg 12.3

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-10-18

Grade Changed

Trust grade A → B

2026-10-18

Rank Moved

Rank dropped 23 spots (#148 → #171)

2026-10-06

Grade Changed

Trust grade B → A

Maintainer Checklist

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

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

74.0

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

Rank Trend

2026-09-29 2026-10-21

Activity & Reach

Stars

11.2k

Forks

570

Last Push

2026-10-21

today

Commits (4 wk)

Downloads (7d)

6,928

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲3

was #174

Analysis

Activity Inputs

74.0 / 100

StarsRepository reach

24.3 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

11.9 / 25

CommunityFork signal

12.8 / 20

Common questions about Tambo

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 4.7/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 OpenUI → Tambo vs Neo → 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-10-18

Grade Changed

Trust grade A → B

2026-10-18

Rank Moved

Rank dropped 23 spots (#148 → #171)

2026-10-06

Grade Changed

Trust grade B → A

2026-10-06

Rank Moved

Rank rose 20 spots (#170 → #150)

2026-10-06

Activity Score Changed

Activity score up 6pts (62 → 68)

2026-09-23

Rank Moved

Rank dropped 85 spots (#78 → #163)

2026-09-21

Rank Moved

Rank rose 91 spots (#169 → #78)

2026-09-07

Rank Moved

Rank dropped 12 spots (#137 → #149)

2026-09-05

Rank Moved

Rank dropped 30 spots (#106 → #136)

2026-09-04

Grade Changed

Trust grade A → B

2026-09-04

Rank Moved

Rank dropped 31 spots (#75 → #106)

2026-09-04

Activity Score Changed

Activity score down 9pts (71 → 62)

2026-09-03

Activity Score Changed

Activity score down 6pts (77 → 71)

2026-08-31

Rank Moved

Rank dropped 10 spots (#63 → #73)

2026-07-28

Newly Listed

First tracked at rank #49

GitHub → Website → 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.4 · Raw JSON

Tambo

How Tambo could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Tambo compares in UI & App Builders

Where the 79.8 comes from

HVTrust dimensions vs the UI & App Builders average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Tambo

Compare Tambo head-to-head

AI agent surface

Maintain Tambo?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in UI & App Builders