Director

AI video agents framework for next-gen video interactions and workflows.

Agent Frameworks Python Grade D Listed MIT
35.3/100
Rank #1235 of 1328
Compare Director

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-01-23 · 240d ago
Recent change
No recent signal change

Is Director safe? Director scores 35.3/100 (Grade D), ranked #1235 of 1328 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 3.6/10; 45% of recent commits are signed; last pushed 2026-01-23. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-08
Rank Moved
Rank dropped 12 spots (#1202 → #1214)
2026-09-07
Rank Moved
Rank dropped 14 spots (#1188 → #1202)
2026-09-06
Rank Moved
Rank dropped 17 spots (#1171 → #1188)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.6/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.
Refresh maintenance signals The repo was last pushed 240 days ago. Fresh activity helps separate stable projects from stale ones.
30.3
Activity sub-score · out of 100
#108

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 →

Signals refreshed 2026-09-20 21:32 UTC · Repo last pushed 240 days ago — may be stale

Rank Trend

2026-08-11 2026-09-20

Activity & Reach

Stars
1.5k
Forks
253
Last Push
2026-01-23
240 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
8
Rank Change
=
was #1235

Analysis

HVTrust Dimensions vs Agent Frameworks

35.3 / 100 · 100.0% confidence

Director Agent Frameworks average (122 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.8 / 25
2.9 below avg 9.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
0.8 below avg 12.4
Maintenance60% last-push freshness · 40% commit activity
0 / 20
13.9 below avg 13.9
AdoptionLog-scaled stars · package downloads
7.6 / 20
3.6 below avg 11.2

Activity Inputs

30.3 / 100
StarsRepository reach
19.1 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
11.2 / 20

Supply Chain Trust

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

Is Director safe?

Public trust evidence for Director is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Director publish package provenance?
No published build provenance is currently detected for Director. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Director have an OpenSSF Scorecard?
Director has an OpenSSF Scorecard score of 3.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 Director actively maintained?
Stale. The repository has not been pushed to in 240 days. Consider whether the project is still being maintained.
What license does Director use?
Director ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Director's commits signed?
45% of the last 100 commits to Director 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: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool 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

Maintain Director?

For maintainers

HVTrust scores Director 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 16Listed 1HVTrust 1Scorecard 1
2026-09-08
Rank Moved
Rank dropped 12 spots (#1202 → #1214)
2026-09-07
Rank Moved
Rank dropped 14 spots (#1188 → #1202)
2026-09-06
Rank Moved
Rank dropped 17 spots (#1171 → #1188)
2026-09-05
Rank Moved
Rank dropped 31 spots (#1140 → #1171)
2026-09-04
Rank Moved
Rank dropped 15 spots (#1125 → #1140)
2026-09-03
Rank Moved
Rank dropped 47 spots (#1078 → #1125)
2026-09-02
Rank Moved
Rank dropped 45 spots (#1033 → #1078)
2026-09-01
Rank Moved
Rank dropped 39 spots (#994 → #1033)
2026-08-31
Rank Moved
Rank dropped 32 spots (#962 → #994)
2026-08-30
Rank Moved
Rank dropped 46 spots (#916 → #962)
2026-08-29
Rank Moved
Rank dropped 48 spots (#868 → #916)
2026-08-28
Scorecard Added
OSSF Scorecard: 3.6/10
2026-08-28
Rank Moved
Rank rose 437 spots (#1305 → #868)
2026-08-28
HVTrust Changed
HVTrust up 22.2pts (13.1 → 35.3)
2026-08-26
Rank Moved
Rank dropped 11 spots (#1292 → #1303)
2026-08-16
Rank Moved
Rank dropped 25 spots (#1267 → #1292)
2026-08-10
Rank Moved
Rank dropped 78 spots (#1188 → #1266)
2026-08-08
Rank Moved
Rank dropped 674 spots (#515 → #1189)
2026-08-06
Newly Listed
First tracked at rank #516

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

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