OpenMontage

World's first open-source, agentic video production system. 12 production pipelines, 100+ tools, 700+ agent skill and pr

Multi-Agent Systems Python Grade C Listed AGPL-3.0
59.4/100
Rank #343 of 1283
Compare OpenMontage

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-14 · 1d ago
Recent change
Rank +6

Is OpenMontage safe? OpenMontage scores 59.4/100 (Grade C), ranked #343 of 1283 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.1/10; 23% of recent commits are signed; last pushed 2026-08-14. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-14
Rank Moved
Rank dropped 24 spots (#317 → #341)
2026-08-13
Rank Moved
Rank rose 42 spots (#359 → #317)
2026-08-13
HVTrust Changed
HVTrust up 3.3pts (57.4 → 60.7)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.1/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.
95.6
Activity sub-score · out of 100
#10

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-08-15 02:04 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-15

Activity & Reach

Stars
48.1k
Forks
6.0k
Last Push
2026-08-14
yesterday
Commits (4 wk)
110
Downloads (7d)
HN mentions (30d)
Open Issues
76
Rank Change
▼2
was #341

Analysis

HVTrust Dimensions vs Multi-Agent Systems

59.4 / 100 · 100.0% confidence

OpenMontage Multi-Agent Systems average (35 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.5 / 25
1.3 above avg 6.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 11.2
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
1.8 above avg 11.0
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.0 above avg 12.9
AdoptionLog-scaled stars · package downloads
11.2 / 20
1.2 above avg 10.0

Activity Inputs

95.6 / 100
StarsRepository reach
28.1 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.1 / 10
OpenSSF Scorecard · scanned Aug 14, 2026
Signed Commits
23%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 4
CI-Tests 10
CII-Best-Practices 0
Code-Review 6
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 10
Vulnerabilities 0

Is OpenMontage safe?

OpenMontage 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 OpenMontage publish package provenance?
No published build provenance is currently detected for OpenMontage. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does OpenMontage have an OpenSSF Scorecard?
OpenMontage has an OpenSSF Scorecard score of 5.1/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 OpenMontage actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does OpenMontage use?
OpenMontage ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenMontage's commits signed?
23% of the last 100 commits to OpenMontage 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
4 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
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 OpenMontage'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-07-17
Provider Added
Runtime surface grew — new detected provider dependencies: ElevenLabs, xAI Grok

Maintain OpenMontage?

For maintainers

HVTrust scores OpenMontage 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
Rank 9Listed 1Scorecard 1Surface 1Score 1HVTrust 1
2026-08-14
Rank Moved
Rank dropped 24 spots (#317 → #341)
2026-08-13
Rank Moved
Rank rose 42 spots (#359 → #317)
2026-08-13
HVTrust Changed
HVTrust up 3.3pts (57.4 → 60.7)
2026-08-13
Activity Score Changed
Activity score up 8pts (88 → 96)
2026-08-12
Rank Moved
Rank rose 17 spots (#376 → #359)
2026-08-10
Rank Moved
Rank dropped 22 spots (#345 → #367)
2026-08-08
Rank Moved
Rank dropped 91 spots (#252 → #343)
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependencies: ElevenLabs, xAI Grok
2026-07-15
Rank Moved
Rank dropped 11 spots (#191 → #202)
2026-07-14
Rank Moved
Rank dropped 13 spots (#178 → #191)
2026-07-13
Rank Moved
Rank dropped 22 spots (#156 → #178)
2026-07-09
Rank Moved
Rank dropped 10 spots (#149 → #159)
2026-07-04
Scorecard Added
OSSF Scorecard: 5.6/10
2026-06-30
Newly Listed
First tracked at rank #314

Embed Badge Badge guide for maintainers →

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