updated 2026-11-05 12:09 UTC

tribe

Repository

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

Multi-Agent Systems TypeScript Needs review MIT

Is tribe safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.4 / 10
Provenance None
Signed commits 66%
Last push 374d ago
Compare tribe

How does it stack up against its Multi-Agent Systems neighbours?

Pick any agent to compare →
Suggest a correction

In detail: tribe scores 27.8/100 (Grade D), ranked #1346 of 1374 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.4/10; 66% of recent commits are signed; last pushed 2025-10-27. Every point is earned from checkable signals — never paid placement. How scoring works →

How tribe 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.

Already done? Suggest a correctionAdd the trust badge
Active listing, but review is needed
  • [4.2.1] no meaningful activity in 12 months (last push 2025-10-27)

Chain of custody

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

  1. Source Partly signed

    github.com/StreetLamb/tribe, MIT, last pushed 2025-10-27. 66% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.4/10 (scanned Nov 3, 2026). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection6
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 1
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    No registry package. tribe is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-09-06 OSSF Scorecard: 4.4/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues tribe’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 tribe compares in Multi-Agent Systems

  1. #39 ChatArena 29.2 +1.4
  2. #40 WorldSeed 28.9 +1.1
  3. #41 tribe 27.8 this agent
  4. #42 SwarmZero 25.8 −2.0
  5. #43 MassGen 19.4 −8.4

Bars show each HVTrust score; the tick marks tribe’s 27.8.

Where the 27.8 comes from

HVTrust dimensions vs the Multi-Agent Systems average

27.8 / 100 · 100.0% confidence

tribe Multi-Agent Systems average (43 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.8 / 25
in line with avg 8.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.5 below avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
0 / 20
13.1 below avg 13.1
AdoptionLog-scaled stars · package downloads
7.3 / 20
3.0 below avg 10.3

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-28
Rank Moved
Rank dropped 96 spots (#1251 → #1347)
2026-10-28
HVTrust Changed
HVTrust down 10.0pts (37.8 → 27.8)
2026-10-27
Warning Issued
Warning: eligibility issues detected
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.4/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.
Refresh maintenance signals The repo was last pushed 374 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[4.2.1] no meaningful activity in 12 months (last push 2025-10-27)
Compare with another agent
View Multi-Agent Systems Report missing data
28.2
Activity sub-score · out of 100
#41
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 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-11-05 12:09 UTC · Repo last pushed 374 days ago — may be stale

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars
1.1k
Forks
137
Last Push
2025-10-27
374 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
=
was #1346

Analysis

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

Common questions about tribe

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?
tribe has an OpenSSF Scorecard score of 4.4/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 tribe actively maintained?
Stale. The repository has not been pushed to in 374 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
How this surface has changed

Detected changes to tribe'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-09-24
Provider Added
Runtime surface grew — new detected provider dependencies: Postgres, Qdrant, Redis

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
Rank 12HVTrust 3Scorecard 1Delisted 1Listed 1Surface 1Warning Issued 1
2026-10-28
Rank Moved
Rank dropped 96 spots (#1251 → #1347)
2026-10-28
HVTrust Changed
HVTrust down 10.0pts (37.8 → 27.8)
2026-10-27
Warning Issued
Warning: eligibility issues detected
2026-10-09
Rank Moved
Rank dropped 11 spots (#1215 → #1226)
2026-09-24
Provider Added
Runtime surface grew — new detected provider dependencies: Postgres, Qdrant, Redis
2026-09-24
Rank Moved
Rank dropped 17 spots (#1179 → #1196)
2026-09-23
Rank Moved
Rank dropped 305 spots (#874 → #1179)
2026-09-23
HVTrust Changed
HVTrust up 11.8pts (27.3 → 39.1)
2026-09-22
Newly Listed
First tracked at rank #874
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Rank Moved
Rank dropped 12 spots (#1174 → #1186)
2026-09-08
Rank Moved
Rank dropped 11 spots (#1163 → #1174)
2026-09-07
Rank Moved
Rank dropped 15 spots (#1148 → #1163)
2026-09-06
Scorecard Added
OSSF Scorecard: 4.4/10
2026-09-06
Rank Moved
Rank rose 172 spots (#1320 → #1148)
2026-09-06
HVTrust Changed
HVTrust up 24.1pts (13.7 → 37.8)
2026-08-26
Rank Moved
Rank dropped 11 spots (#1286 → #1297)
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)
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 27.8 Grade D
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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON