OpenFilm
The open source AI video agent: turns any coding agent into a video agent, with an editor to change anything it makes.
Is OpenFilm safe? Strong public trust posture, backed by multiple independent signals.
Compare OpenFilm
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: OpenFilm scores 86.6/100 (Grade A), ranked #11 of 396 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.6/10; 61% of recent commits are signed; no published advisory affects its latest release (openfilm); last pushed 2026-11-16. Every point is earned from checkable signals — never paid placement. How scoring works →
How OpenFilm 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 from 5.6 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Fuzzing 0 +5.7 → 92.3 A · #3 of 396
- Sign every commit61% signed today +1.6 → 88.2 A · #7 of 396
Chain of custody
Scanners check what the code says. This traces who ships OpenFilm 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 and, for skills, AST02 Supply Chain Compromise.
-
Source Partly signed
github.com/openfilm/openfilm, MIT, last pushed 2026-11-16. 61% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.6/10 (scanned Nov 15, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 10CII-Best-Practices 0Code-Review 0Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 0Packaging -1Pinned-Dependencies 0SAST 3Security-Policy 10Signed-Releases 0Token-Permissions 10Vulnerabilities 10 -
Published packages Linked and attested
- npm openfilm Source link points back to this repo Build provenance attested
-
What you install today No known advisories
Latest release checked: openfilm 0.3.2. No published advisory affects it (OSV, checked 2026-11-16).
Changes to this chain
- 2026-11-13 OSSF Scorecard: 6.0/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues OpenFilm’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 the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.
How OpenFilm compares in Agent Skills
- #9 MisakaNet 87.8 +1.2
- #10 Cc Safety Net 87.7 +1.1
- #11 OpenFilm 86.6 this agent
- #12 Oh My Claudecode 85.8 −0.8
- #13 Claudecodeui 85.5 −1.1
Bars show each HVTrust score; the tick marks OpenFilm’s 86.6.
Where the 86.6 comes from
HVTrust dimensions vs the Agent Skills average
86.6 / 100 · 100.0% confidenceOpenFilm Agent Skills average (396 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 A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
86.9 / 100Common questions about OpenFilm
Does OpenFilm publish package provenance?
Does OpenFilm have an OpenSSF Scorecard?
Is OpenFilm actively maintained?
What license does OpenFilm use?
Are OpenFilm'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 →
- browser
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain OpenFilm?
For maintainers
HVTrust scores OpenFilm 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/openfilm)
<a href="https://hvtracker.net/agents/openfilm"><img src="https://hvtracker.net/badge/openfilm.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON