Is swarmclaw safe to use?

swarmclaw has an HVTrust score of 39.8/100 (Grade D), ranked #1171 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for swarmclaw?

swarmclaw scores 39.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 673 GitHub stars and is categorized under Multi-Agent Systems.

swarmclaw

swarmclawai/swarmclaw

Open-source self-hosted AI agent runtime and multi-agent framework for autonomous agent swarms. Agent memory, MCP tools,

Multi-Agent Systems TypeScript Grade D Listed MIT

39.8/100

Rank #1171 of 1328

Compare swarmclaw

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 C · 2/5 signals

Last push

2026-06-30 · 80d ago

Recent change

Rank +2

Is swarmclaw safe? swarmclaw scores 39.8/100 (Grade D), ranked #1171 of 1328 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 2.9/10; 5% of recent commits are signed; last pushed 2026-06-30. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

#26 Swarm by OpenAI — 45.5 (D) → #27 MiroFlow — 42.9 (D) → #29 tribe — 37.8 (D) → #30 GPTSwarm — 37.3 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-17

Rank Moved

Rank dropped 11 spots (#1158 → #1169)

2026-09-12

Rank Moved

Rank dropped 10 spots (#1148 → #1158)

2026-09-11

Rank Moved

Rank dropped 28 spots (#1120 → #1148)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.9/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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

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

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

41.0

Activity sub-score · out of 100

#28

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 →

Rank Trend

2026-08-11 2026-09-18

Activity & Reach

Stars

673

Forks

137

Last Push

2026-06-30

80 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #1169

Analysis

HVTrust Dimensions vs Multi-Agent Systems

39.8 / 100 · 100.0% confidence

swarmclaw Multi-Agent Systems average (38 agents)

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

3.9 / 25

4.5 below avg 8.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

in line with avg 11.2

Transparency50% declared license · 50% OSSF Scorecard

11.0 / 17

1.0 below avg 12.0

Maintenance60% last-push freshness · 40% commit activity

6.7 / 20

5.7 below avg 12.4

AdoptionLog-scaled stars · package downloads

6.8 / 20

3.3 below avg 10.1

Activity Inputs

41.0 / 100

StarsRepository reach

17.0 / 30

FreshnessLast push recency

13.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

10.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.9 / 10

OpenSSF Scorecard · scanned Sep 16, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 1

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 2

Packaging 10

Pinned-Dependencies 3

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is swarmclaw safe?

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

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

Does swarmclaw have an OpenSSF Scorecard?

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

Slowing down. Last push was 80 days ago — keep an eye on whether activity resumes.

What license does swarmclaw use?

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

Are swarmclaw's commits signed?

5% of the last 100 commits to swarmclaw 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

high confidence

Implemented

swarmclaw appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

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

Tool / Plugin Surface

high confidence

Extensions

Extension based plugin/integration surface detected.

browser

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

For maintainers

HVTrust scores swarmclaw 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-09-17

Rank Moved

Rank dropped 11 spots (#1158 → #1169)

2026-09-12

Rank Moved

Rank dropped 10 spots (#1148 → #1158)

2026-09-11

Rank Moved

Rank dropped 28 spots (#1120 → #1148)

2026-09-09

Rank Moved

Rank dropped 11 spots (#1106 → #1117)

2026-09-07

Rank Moved

Rank dropped 28 spots (#1070 → #1098)

2026-09-06

Rank Moved

Rank dropped 13 spots (#1057 → #1070)

2026-09-05

Rank Moved

Rank dropped 46 spots (#1011 → #1057)

2026-09-04

Rank Moved

Rank dropped 24 spots (#987 → #1011)

2026-09-03

Rank Moved

Rank dropped 56 spots (#931 → #987)

2026-09-02

Scorecard Added

OSSF Scorecard: 3.5/10

2026-09-02

Rank Moved

Rank rose 351 spots (#1282 → #931)

2026-09-02

HVTrust Changed

HVTrust up 24.3pts (17.7 → 42.0)

2026-08-31

Rank Moved

Rank dropped 10 spots (#1263 → #1273)

2026-08-30

Rank Moved

Rank dropped 12 spots (#1251 → #1263)

2026-08-29

Rank Moved

Rank dropped 13 spots (#1238 → #1251)

2026-08-28

Rank Moved

Rank dropped 12 spots (#1226 → #1238)

2026-08-27

Rank Moved

Rank dropped 12 spots (#1214 → #1226)

2026-08-26

Rank Moved

Rank dropped 41 spots (#1173 → #1214)

2026-08-16

Rank Moved

Rank dropped 24 spots (#1146 → #1170)

2026-08-10

Rank Moved

Rank dropped 67 spots (#1074 → #1141)

2026-08-08

Rank Moved

Rank dropped 568 spots (#500 → #1068)

2026-08-06

Rank Moved

Rank dropped 33 spots (#457 → #490)

2026-08-03

Newly Listed

First tracked at rank #457

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/swarmclaw.svg)](https://hvtracker.net/agents/swarmclaw)
            
HTML:
            <a href="https://hvtracker.net/agents/swarmclaw"><img src="https://hvtracker.net/badge/swarmclaw.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.3 · Raw JSON