updated 2026-10-10 20:07 UTC

Capcut Cli

Repository Website

Independent, unofficial CLI to edit CapCut and JianYing (剪映) projects — subtitles, timing, speed, volume, templates, cut long-form to shorts. No API needed, reads draft_content.json and draft_info.json (剪映草稿) directly. Not affiliated with ByteDance.

Agent Skills JavaScript Listed MIT

Is Capcut Cli safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.0 / 10
Provenance None
Signed commits 97%
Last push yesterday
Advisories None known
Compare Capcut Cli

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Capcut Cli scores 68.8/100 (Grade B), ranked #34 of 371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; 97% of recent commits are signed; no published advisory affects its latest release (capcut-cli); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Capcut Cli 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Capcut Cli 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 Signed

    github.com/renezander030/capcut-cli, MIT, last pushed 2026-10-09. 97% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.0/10 (scanned Oct 10, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies5
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 5
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Linked, not attested

    • npm capcut-cli Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: capcut-cli 0.29.0. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Capcut Cli.

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 Capcut Cli’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.

Signed credential (JSON) How to verify

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 Capcut Cli compares in Agent Skills

  1. #32 Boss Skill 69.9 +1.1
  2. #33 ClawBio 69.9 +1.1
  3. #34 Capcut Cli 68.8 this agent
  4. #35 Career Ops 68.4 −0.4
  5. #36 RuView 68.3 −0.5

Bars show each HVTrust score; the tick marks Capcut Cli’s 68.8.

Where the 68.8 comes from

HVTrust dimensions vs the Agent Skills average

68.8 / 100 · 100.0% confidence

Capcut Cli Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.1 / 25
3.3 above avg 7.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
0.8 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
17.6 / 20
3.5 above avg 14.1
AdoptionLog-scaled stars · package downloads
11.8 / 20
2.8 above avg 9.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/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.
Compare with another agent Get email alerts for Capcut Cli View Agent Skills Report missing data
69.5
Activity sub-score · out of 100
#34
In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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-10-10 20:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars
860
Forks
89
Last Push
2026-10-09
yesterday
Commits (4 wk)
26
Downloads (7d)
3,594
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
=
was #34

Analysis

Activity Inputs

69.5 / 100
StarsRepository reach
17.6 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
17.9 / 25
CommunityFork signal
9.1 / 20

Common questions about Capcut Cli

Capcut Cli 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 Capcut Cli publish package provenance?
No published build provenance is currently detected for Capcut Cli. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Capcut Cli have an OpenSSF Scorecard?
Capcut Cli has an OpenSSF Scorecard score of 5.0/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 Capcut Cli actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Capcut Cli use?
Capcut Cli ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Capcut Cli's commits signed?
97% of the last 100 commits to Capcut Cli 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
medium confidence
Implemented
Capcut Cli appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 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
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
How this surface has changed

Detected changes to Capcut Cli'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-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Capcut Cli?

For maintainers

HVTrust scores Capcut Cli 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
HVTrust 3Rank 3Grade 3Listed 2Delisted 1MCP 1Surface 1Surface 1
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 226 spots (#261 → #35)
2026-09-23
HVTrust Changed
HVTrust up 38.1pts (31.3 → 69.4)
2026-09-22
Newly Listed
First tracked at rank #261
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-04
Grade Changed
Trust grade D → B
2026-09-04
Rank Moved
Rank rose 177 spots (#193 → #16)
2026-09-04
HVTrust Changed
HVTrust up 25.2pts (45.8 → 71.0)
2026-09-03
Grade Changed
Trust grade B → D
2026-09-03
Rank Moved
Rank dropped 177 spots (#16 → #193)
2026-09-03
HVTrust Changed
HVTrust down 25.0pts (70.8 → 45.8)
2026-08-26
Newly Listed
First tracked at rank #11
GitHub → Website → npm: capcut-cli

Embed Badge Badge guide for maintainers →

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