updated 2026-11-11 00:08 UTC

Huashu Motion

Repository by alchaincyf

让你的agent一键直出商业级产品宣传片：会作曲，能指着画面改。Commercial-grade launch films by your coding agent — point at the frame to change it.

Agent Skills JavaScript Listed MIT

Is Huashu Motion safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard No result
Provenance Attested
Signed commits 0%
Last push yesterday
Advisories None known
Compare Huashu Motion

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Huashu Motion scores 67.1/100 (Grade B), ranked #51 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; no OSSF Scorecard result yet; recent commits are unsigned; no published advisory affects its latest release (huashu-motion); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Huashu Motion 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 Huashu Motion 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 Unsigned

    github.com/alchaincyf/huashu-motion, MIT, last pushed 2026-11-10. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Not checked

    No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.

  3. Published packages Linked and attested

    • npm huashu-motion Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: huashu-motion 0.4.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

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

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 Huashu Motion’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 Huashu Motion compares in Agent Skills

  1. #49 Orchestkit 67.1 ±0
  2. #50 Thesvg 67.1 ±0
  3. #51 Huashu Motion 67.1 this agent
  4. #52 Diagram Design 67.0 −0.1
  5. #53 Claude Obsidian 66.7 −0.4

Bars show each HVTrust score; the tick marks Huashu Motion’s 67.1.

Where the 67.1 comes from

HVTrust dimensions vs the Agent Skills average

67.1 / 100 · 100.0% confidence

Huashu Motion Agent Skills average (396 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.5 / 25
0.6 below avg 8.1
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.5 above avg 11.5
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.7 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
16.9 / 20
2.8 above avg 14.1
AdoptionLog-scaled stars · package downloads
12.2 / 20
3.1 above avg 9.1

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-11-10
Newly Listed
First tracked at rank #50
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View Agent Skills Report missing data
72.4
Activity sub-score · out of 100
#51
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-11-11 00:08 UTC · Repo last pushed yesterday

Activity & Reach

Stars
2.6k
Forks
260
Last Push
2026-11-10
yesterday
Commits (4 wk)
17
Downloads (7d)
1,072
npm
HN mentions (30d)
—
Open Issues
3
Rank Change
▼1
was #50

Analysis

Activity Inputs

72.4 / 100
StarsRepository reach
20.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
15.7 / 25
CommunityFork signal
11.2 / 20

Common questions about Huashu Motion

Huashu Motion 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 Huashu Motion publish package provenance?
Yes. Huashu Motion's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Huashu Motion have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Huashu Motion. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Huashu Motion actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Huashu Motion use?
Huashu Motion ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Huashu Motion's commits signed?
0% of the last 100 commits to Huashu Motion 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
None detected
No clear plugin system or broad tool 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

Maintain Huashu Motion?

For maintainers

HVTrust scores Huashu Motion 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
Listed 1
2026-11-10
Newly Listed
First tracked at rank #50
GitHub → npm: huashu-motion

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 67.1 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/huashu-motion.svg)](https://hvtracker.net/agents/huashu-motion)
HTML:
<a href="https://hvtracker.net/agents/huashu-motion"><img src="https://hvtracker.net/badge/huashu-motion.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON