Is tribe safe to use?

tribe has an HVTrust score of 13.7/100 (Grade D), ranked #1287 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for tribe?

tribe scores 13.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.1k GitHub stars and is categorized under Multi-Agent Systems.

tribe

StreetLamb/tribe

Low code tool to rapidly build and coordinate multi-agent teams

Multi-Agent Systems TypeScript Grade D Listed MIT

13.7/100

Rank #1287 of 1308

Compare tribe

How does it stack up against its Multi-Agent Systems 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 D · 1/5 signals

Last push

2025-10-27 · 296d ago

Recent change

Rank

Is tribe safe? tribe scores 13.7/100 (Grade D), ranked #1287 of 1308 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 66% of recent commits are signed; last pushed 2025-10-27. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

#32 MassGen — 17.9 (D) → #33 WorldSeed — 15.1 (D) → #34 GPTSwarm — 14.0 (D) → #36 KaibanJS — 12.6 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-16

Rank Moved

Rank dropped 25 spots (#1262 → #1287)

2026-08-10

Rank Moved

Rank dropped 79 spots (#1182 → #1261)

2026-08-08

Rank Moved

Rank dropped 669 spots (#514 → #1183)

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Refresh maintenance signals The repo was last pushed 296 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for tribe View Multi-Agent Systems Report missing data

28.2

Activity sub-score · out of 100

#35

In Multi-Agent Systems

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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

1.1k

Forks

137

Last Push

2025-10-27

296 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #1287

Analysis

HVTrust Dimensions vs Multi-Agent Systems

13.7 / 100 · 50.0% confidence

tribe Multi-Agent Systems average (36 agents)

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

3.3 / 25

2.8 below avg 6.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

in line with avg 11.2

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

2.4 below avg 10.9

Maintenance60% last-push freshness · 40% commit activity

0 / 20

13.0 below avg 13.0

AdoptionLog-scaled stars · package downloads

7.3 / 20

2.6 below avg 9.9

Activity Inputs

28.2 / 100

StarsRepository reach

18.2 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

10.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

66%

of last 100 commits verified

Is tribe safe?

Public trust evidence for tribe 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 tribe publish package provenance?

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

Does tribe have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for tribe. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is tribe actively maintained?

Stale. The repository has not been pushed to in 296 days. Consider whether the project is still being maintained.

What license does tribe use?

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

Are tribe's commits signed?

66% of the last 100 commits to tribe 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

3 detected

Public provider/service dependencies detected.

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

Tool / Plugin Surface

high confidence

1 tags

Broad capability areas detected.

database

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 tribe?

For maintainers

HVTrust scores tribe 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-16

Rank Moved

Rank dropped 25 spots (#1262 → #1287)

2026-08-10

Rank Moved

Rank dropped 79 spots (#1182 → #1261)

2026-08-08

Rank Moved

Rank dropped 669 spots (#514 → #1183)

2026-08-06

Newly Listed

First tracked at rank #517

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Multi-Agent Systems

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