Is Qiaomu Cut Skill safe to use?

Qiaomu Cut Skill has an HVTrust score of 48.0/100 (Grade D), ranked #274 of 371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Qiaomu Cut Skill?

Qiaomu Cut Skill scores 48.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 374 GitHub stars and is categorized under Agent Skills.

Qiaomu Cut Skill

Repository

乔木智能视频导演 Skill：素材治理、双语字幕、品牌包装与可复现渲染 | Agent-native video director with governed sourcing and verifiable rendering

Agent Skills JavaScript Listed MIT

Is Qiaomu Cut Skill safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.7 / 10

Provenance None

Signed commits 100%

Last push 2d ago

Compare Qiaomu Cut Skill

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Qiaomu Cut Skill scores 48.0/100 (Grade D), ranked #274 of 371 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 2.7/10; 100% of recent commits are signed; last pushed 2026-10-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How Qiaomu Cut Skill 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 2.7 to 9.0lowest checks: Branch-Protection 0, CI-Tests 0, CII-Best-Practices 0 +13.1 → 61.1 C · #92 of 371

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Qiaomu Cut Skill and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

Source Signed

github.com/joeseesun/qiaomu-cut-skill, MIT, last pushed 2026-10-13. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 2.7/10 (scanned Oct 10, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependenciesn/a
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 3

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 10
Published packages None

No registry package. Qiaomu Cut Skill is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

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

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

GitHub repository data
Package downloads (missing)
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Qiaomu Cut Skill’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 Qiaomu Cut Skill compares in Agent Skills

Bars show each HVTrust score; the tick marks Qiaomu Cut Skill’s 48.0.

Where the 48.0 comes from

HVTrust dimensions vs the Agent Skills average

48.0 / 100 · 100.0% confidence

Qiaomu Cut Skill Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

8.4 / 25

in line with avg 8.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

10.8 / 17

1.3 below avg 12.1

Maintenance60% last-push freshness · 40% commit activity

12.8 / 20

1.3 below avg 14.1

AdoptionLog-scaled stars · package downloads

6.2 / 20

2.8 below 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-28

Rank Moved

Rank rose 43 spots (#309 → #266)

2026-09-28

HVTrust Changed

HVTrust up 5.3pts (42.4 → 47.7)

2026-09-28

Activity Score Changed

Activity score up 14pts (38 → 51)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.7/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 Qiaomu Cut Skill View Agent Skills Report missing data

53.8

Activity sub-score · out of 100

#274

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 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 →

Rank Trend

2026-09-29 2026-10-15

Activity & Reach

Stars

374

Forks

Last Push

2026-10-13

2 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #271

Analysis

Activity Inputs

53.8 / 100

StarsRepository reach

15.4 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

6.0 / 25

CommunityFork signal

7.5 / 20

Common questions about Qiaomu Cut Skill

Public trust evidence for Qiaomu Cut Skill 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 Qiaomu Cut Skill publish package provenance?

No published build provenance is currently detected for Qiaomu Cut Skill. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Qiaomu Cut Skill have an OpenSSF Scorecard?

Qiaomu Cut Skill has an OpenSSF Scorecard score of 2.7/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 Qiaomu Cut Skill actively maintained?

Actively maintained. The repository was pushed to within the last 2 day(s).

What license does Qiaomu Cut Skill use?

Qiaomu Cut Skill ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Qiaomu Cut Skill's commits signed?

100% of the last 100 commits to Qiaomu Cut Skill 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

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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 Qiaomu Cut Skill?

For maintainers

HVTrust scores Qiaomu Cut Skill 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

2026-09-28

Rank Moved

Rank rose 43 spots (#309 → #266)

2026-09-28

HVTrust Changed

HVTrust up 5.3pts (42.4 → 47.7)

2026-09-28

Activity Score Changed

Activity score up 14pts (38 → 51)

2026-09-25

Rank Moved

Rank dropped 24 spots (#281 → #305)

2026-09-23

Rank Moved

Rank dropped 10 spots (#271 → #281)

2026-09-23

HVTrust Changed

HVTrust up 12.4pts (30.3 → 42.7)

2026-09-22

Newly Listed

First tracked at rank #271

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-11

Rank Moved

Rank dropped 12 spots (#251 → #263)

2026-09-08

Rank Moved

Rank dropped 10 spots (#227 → #237)

2026-09-05

Rank Moved

Rank dropped 12 spots (#207 → #219)

2026-09-01

Rank Moved

Rank dropped 15 spots (#170 → #185)

2026-08-31

Rank Moved

Rank dropped 18 spots (#152 → #170)

2026-08-30

Rank Moved

Rank dropped 29 spots (#123 → #152)

2026-08-29

Rank Moved

Rank dropped 28 spots (#95 → #123)

2026-08-28

Rank Moved

Rank dropped 22 spots (#73 → #95)

2026-08-27

Rank Moved

Rank dropped 20 spots (#53 → #73)

2026-08-26

Newly Listed

First tracked at rank #53

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/qiaomu-cut-skill.svg)](https://hvtracker.net/agents/qiaomu-cut-skill)
            
HTML:
            <a href="https://hvtracker.net/agents/qiaomu-cut-skill"><img src="https://hvtracker.net/badge/qiaomu-cut-skill.svg" alt="HVTrust"></a>

Other agents in Agent Skills

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.4 · Raw JSON

Qiaomu Cut Skill

How Qiaomu Cut Skill could raise its score

Chain of custody

Source Signed

Review and release Weak

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Qiaomu Cut Skill compares in Agent Skills

Where the 48.0 comes from

HVTrust dimensions vs the Agent Skills average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Qiaomu Cut Skill

AI agent surface

Maintain Qiaomu Cut Skill?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Skills