updated 2026-10-03 16:08 UTC

Cumora

Repository Website

Where agent teams gather. Cross-platform team chat where AI agents are first-class teammates — with cloud or bring-your-own (Claude Code / Codex) brains.

Multi-Agent Systems TypeScript Listed MIT

Is Cumora safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.6 / 10
Provenance None
Signed commits 70%
Last push today
Compare Cumora

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

Pick any agent to compare →
Suggest a correction

In detail: Cumora scores 56.7/100 (Grade C), ranked #743 of 1346 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 3.6/10; 70% of recent commits are signed; last pushed 2026-10-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cumora 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

Chain of custody

Scanners check what the code says. This traces who ships Cumora and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run.

  1. Source Partly signed

    github.com/yetone/cumora, MIT, last pushed 2026-10-03. 70% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

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

  3. Published packages None

    No registry package. Cumora 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-10-02 OSSF Scorecard: 3.6/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 Cumora’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 Cumora compares in Multi-Agent Systems

  1. #18 Rowboat 59.4 +2.7
  2. #19 Agent Squad 57.6 +0.9
  3. #20 Cumora 56.7 this agent
  4. #21 sympozium 55.7 −1.0
  5. #22 OpenMontage 55.3 −1.4

Bars show each HVTrust score; the tick marks Cumora’s 56.7.

Where the 56.7 comes from

HVTrust dimensions vs the Multi-Agent Systems average

56.7 / 100 · 100.0% confidence

Cumora Multi-Agent Systems average (42 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.0 / 25
in line with avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 11.1
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.9 above avg 13.1
AdoptionLog-scaled stars · package downloads
8.6 / 20
1.5 below avg 10.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-02
Scorecard Added
OSSF Scorecard: 3.6/10
2026-10-02
Grade Changed
Trust grade D → C
2026-10-02
Rank Moved
Rank rose 582 spots (#1334 → #752)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.6/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.
Compare with another agent Get email alerts for Cumora View Multi-Agent Systems Report missing data
84.2
Activity sub-score · out of 100
#20
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 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 →

Signals refreshed 2026-10-03 16:08 UTC · Repo last pushed today

Rank Trend

2026-10-01 2026-10-03

Activity & Reach

Stars
3.9k
Forks
513
Last Push
2026-10-03
today
Commits (4 wk)
138
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
12
Rank Change
▲9
was #752

Analysis

Activity Inputs

84.2 / 100
StarsRepository reach
21.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.6 / 20

Common questions about Cumora

Cumora 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 Cumora publish package provenance?
No published build provenance is currently detected for Cumora. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Cumora have an OpenSSF Scorecard?
Cumora has an OpenSSF Scorecard score of 3.6/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 Cumora actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Cumora use?
Cumora ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Cumora's commits signed?
70% of the last 100 commits to Cumora 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: API keys or service config markers documented.
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 Cumora?

For maintainers

HVTrust scores Cumora 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
Listed 1HVTrust 1Rank 1Grade 1Scorecard 1
2026-10-02
Scorecard Added
OSSF Scorecard: 3.6/10
2026-10-02
Grade Changed
Trust grade D → C
2026-10-02
Rank Moved
Rank rose 582 spots (#1334 → #752)
2026-10-02
HVTrust Changed
HVTrust up 33.1pts (23.4 → 56.5)
2026-10-01
Newly Listed
First tracked at rank #1334
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 56.7 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/cumora.svg)](https://hvtracker.net/agents/cumora)
HTML:
<a href="https://hvtracker.net/agents/cumora"><img src="https://hvtracker.net/badge/cumora.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