OpenFilm

The open source AI video agent: turns any coding agent into a video agent, with an editor to change anything it makes.

Agent Skills TypeScript Listed MIT

Is OpenFilm safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.6 / 10
Provenance Attested
Signed commits 61%
Last push yesterday
Advisories None known
Compare OpenFilm
Suggest a correction

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.

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.

  1. 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.

  2. 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 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 3
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 10
    Vulnerabilities 10
  3. Published packages Linked and attested

    • npm openfilm Source link points back to this repo Build provenance attested
  4. 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

  1. #9 MisakaNet 87.8 +1.2
  2. #10 Cc Safety Net 87.7 +1.1
  3. #11 OpenFilm 86.6 this agent
  4. #12 Oh My Claudecode 85.8 −0.8
  5. #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% confidence

OpenFilm Agent Skills average (396 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.5 / 25
9.3 above avg 8.2
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.5 above avg 11.5
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
1.1 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
5.9 above avg 14.0
AdoptionLog-scaled stars · package downloads
14.9 / 20
5.7 above avg 9.2

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Recent Changes
2026-11-13
Scorecard Added
OSSF Scorecard: 6.0/10
2026-11-13
Grade Changed
Trust grade B → A
2026-11-13
Rank Moved
Rank rose 15 spots (#26 → #11)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.6/10. Tighten the weakest checks to improve public safety evidence.
86.9
Activity sub-score · out of 100
#11

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 →

Signals refreshed 2026-11-17 12:07 UTC · Repo last pushed yesterday

Rank Trend

2026-11-10 2026-11-17

Activity & Reach

Stars
8.0k
Forks
780
Last Push
2026-11-16
yesterday
Commits (4 wk)
216
Downloads (7d)
14,356
npm
HN mentions (30d)
—
Open Issues
24
Rank Change
=
was #11

Analysis

Activity Inputs

86.9 / 100
StarsRepository reach
23.4 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.5 / 20

Common questions about OpenFilm

Public supply-chain signals for OpenFilm are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but OpenFilm carries less obvious unverified-evidence risk than projects with thin signals.
Does OpenFilm publish package provenance?
Yes. OpenFilm's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does OpenFilm have an OpenSSF Scorecard?
OpenFilm has an OpenSSF Scorecard score of 5.6/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 OpenFilm actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does OpenFilm use?
OpenFilm ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenFilm's commits signed?
61% of the last 100 commits to OpenFilm 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
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • browser
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • 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
Listed 1HVTrust 1Rank 1Grade 1Scorecard 1
2026-11-13
Scorecard Added
OSSF Scorecard: 6.0/10
2026-11-13
Grade Changed
Trust grade B → A
2026-11-13
Rank Moved
Rank rose 15 spots (#26 → #11)
2026-11-13
HVTrust Changed
HVTrust up 9.8pts (77.3 → 87.1)
2026-11-10
Newly Listed
First tracked at rank #26

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 86.6 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/openfilm.svg)](https://hvtracker.net/agents/openfilm)
HTML:
<a href="https://hvtracker.net/agents/openfilm"><img src="https://hvtracker.net/badge/openfilm.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
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