Multica
Make humans and AI agents work as one team — open-source and self-hostable.
Is Multica safe? Promising trust profile, but some evidence still deserves review.
Compare Multica
How does it stack up against its Multi-Agent Systems neighbours?
Pick any agent to compare →In detail: Multica scores 65.7/100 (Grade B), ranked #451 of 1325 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 5.0/10; 100% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How Multica compares in Multi-Agent Systems
- #5 Agency Swarm 67.5 +1.8
- #6 Ruflo 66.6 +0.9
- #7 Multica 65.7 this agent
- #8 Concordia 65.5 −0.2
- #9 agent-swarm 65.3 −0.4
Bars show each HVTrust score; the tick marks Multica’s 65.7.
Where the 65.7 comes from
HVTrust dimensions vs the Multi-Agent Systems average
65.7 / 100 · 100.0% confidenceMultica Multi-Agent Systems average (38 agents)
Quick Trust Read
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 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
Activity & Reach
Analysis
Activity Inputs
96.1 / 100Supply Chain Trust
Common questions about Multica
Does Multica publish package provenance?
Does Multica have an OpenSSF Scorecard?
Is Multica actively maintained?
What license does Multica use?
Are Multica's commits signed?
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 Multica head-to-head
AI agent surface
MCP, providers, tool surface
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Multica'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.
Maintain Multica?
For maintainers
HVTrust scores Multica 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/multica)
<a href="https://hvtracker.net/agents/multica"><img src="https://hvtracker.net/badge/multica.svg" alt="HVTrust"></a>
Other agents in Multi-Agent Systems
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