MassGen
Website
🚀 MassGen is an open-source multi-agent scaling system that runs in your terminal, autonomously orchestrating frontier models and agents to collaborate, reason, and produce high-quality results. | Join us on Discord: discord.massgen.ai
Is MassGen safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare MassGen
How does it stack up against its Multi-Agent Systems neighbours?
Pick any agent to compare →In detail: MassGen scores 19.7/100 (Grade D), ranked #1375 of 1378 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 15% of recent commits are signed; last pushed 2026-06-12. Every point is earned from checkable signals — never paid placement. How scoring works →
How MassGen 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.
- Raise the OSSF Scorecard to 9.0no OSSF Scorecard result yet +29.9 → 49.6 D · #32 of 43
- Publish build provenance for its packagesPyPI Trusted Publishing attestations +25.7 → 45.4 D · #32 of 43
- Sign every commit15% signed today +2.8 → 22.5 D · #43 of 43
Chain of custody
Scanners check what the code says. This traces who ships MassGen and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/massgen/MassGen, NOASSERTION, last pushed 2026-06-12. 15% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Not checked
No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.
-
Published packages Not linked
- PyPI massgen Source link points to this repo's current name No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
Changes to this chain
- 2026-10-02 Provenance drift warning cleared (now: unknown)
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks (missing)
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues MassGen’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.
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 MassGen compares in Multi-Agent Systems
- #39 KaibanJS 31.2 +11.5
- #40 WorldSeed 29.8 +10.1
- #41 ChatArena 29.2 +9.5
- #42 SwarmZero 26.4 +6.7
- #43 MassGen 19.7 this agent
Bars show each HVTrust score; the tick marks MassGen’s 19.7.
Where the 19.7 comes from
HVTrust dimensions vs the Multi-Agent Systems average
19.7 / 100 · 67.0% confidenceMassGen Multi-Agent Systems average (43 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 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
Activity & Reach
Analysis
Activity Inputs
35.6 / 100Common questions about MassGen
Does MassGen publish package provenance?
Does MassGen have an OpenSSF Scorecard?
Is MassGen actively maintained?
What license does MassGen use?
Are MassGen'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.
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 →
- Anthropic
- ElevenLabs
- Google Gemini
- Groq
- Multi-provider (LiteLLM)
- OpenAI
- OpenRouter
- Redis
- Together AI
- xAI Grok
- code
- database
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to MassGen'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 MassGen?
For maintainers
HVTrust scores MassGen 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/massgen)
<a href="https://hvtracker.net/agents/massgen"><img src="https://hvtracker.net/badge/massgen.svg" alt="HVTrust"></a>
Other agents in Multi-Agent Systems
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON