Jianying Headless collected 603 GitHub stars during its first three days, then reached 740 by the time MrKeyoor checked it on September 18. That is a fast start for a repository whose custom license bars commercial use, client delivery and even internal business operations unless the author gives written permission. The code is publicly readable, but the permission to use it is much narrower than the star count suggests.
The repository automates Jianying Pro video editing on an Apple Silicon Mac. It can turn a JSON editing plan into a native, editable draft, modify an existing multitrack project in a separate copy and invoke Jianying's own engine to export an MP4. Its README is equally direct about what it is missing: no Jianying installer, official libraries, online templates, account access or blanket support for different app versions.
GitHub currently identifies the repository as public, while its description calls the release a "private source preview" and its setup instructions say cloning requires an authorized account. The separately published Agent Skill repeats that access requirement. The repository metadata and the written instructions therefore describe different access states. Anyone evaluating the project needs to read what is visible today without assuming that continued public access, redistribution or commercial use has been granted.
The headless name needs unpacking
Here, "headless" means the tool can build and export without driving Jianying's interface. It does not mean Jianying has been replaced. The runtime code expects the official application at a fixed path, checks its bundle identifier and signing team, then links against the installed libvideoeditor.dylib. The supported draft profiles are Jianying Pro 11.4.0 and 11.4.2; native export accepts 11.4.2 only.
The project instructions name Apple Silicon, macOS 26.0 or later, Python 3.9, FFmpeg, ffprobe and Xcode command-line tools. A build made with a different compiler or SDK is accepted only if its binary matches a pinned SHA-256 digest. That makes the current release a snapshot of one known setup, rather than a general automation layer for every Mac running the editor.
A user supplies media paths, a canvas and timeline segments in JSON, then runs the project's doctor, build and verification commands. The documented entry point looks like this:
python3 skills/yichen-jianying-edit/scripts/headless_draft.py doctor
python3 skills/yichen-jianying-edit/scripts/headless_draft.py build \
--plan /absolute/path/to/plan.json --out "$PWD/work/new-build"
python3 skills/yichen-jianying-edit/scripts/headless_draft.py verify-build \
--build "$PWD/work/new-build"
A plan can describe cuts, speed and volume changes, multiple tracks, picture-in-picture, titles, local audio and linear keyframes. The current support table also lists six static mask shapes, a dissolve transition and three captured visual resources. Curved speed ramps, arbitrary animation and automatic access to online assets remain outside the stated scope.
Most of the engineering is about refusing unsafe work
The repository does more than write Jianying project files. Its doctor routine checks the app version, build number, bundle ID, library digest and code signature before allowing native writes. The Agent Skill's Python entry point pins the hashes of the engine modules and resource catalogs. A changed or missing component stops execution and asks for a fresh review instead of accepting the new file.
New builds must live outside Jianying's active draft directory. Editing an existing draft creates an independent copy, and publication means registering a draft on the local Jianying home screen, not uploading a video. The Skill instructions tell an agent to wait until the editor is closed, preserve the source media and keep failed work in place for inspection rather than retrying with effects removed.
Export is also separated from ordinary draft creation. The user has to ask for a finished video, and the tool writes render.mp4 into a new directory. According to the README, the export process does not read account data by default and does not add media, output, logs or compiled binaries to Git. Those boundaries matter because the bridge calls an internal interface from a proprietary editor, not a documented official SDK.
The test report is detailed, with important gaps
The project's own verification record reports 10 of 10 packaging tests and 149 of 149 existing functional checks on September 15. Its new-package smoke run built a two-second project with three tracks and four segments, then exported 60 frames at 640 by 360 pixels with H.264 video and AAC audio. The resulting file decoded fully, and frames sampled at 0.5 and 1.5 seconds showed the expected test image, rotated overlay, Chinese subtitle and sped-up source.
Those numbers come from the maintainer's machine and fixtures. The same verification page says the release snapshot has not passed installation on a second clean machine. It also did not cover opening, saving and cold-reopening the new snapshot in Jianying's interface, subjective audio review, other toolchains or every combination of effects. The commands are available for reproduction, but several historical tests need local fixtures that the repository does not distribute.
The page also records failures and edge conditions. Compound clips can be built and exported as frozen snapshots, but registering them on the editor's home screen is deliberately blocked. Low-resolution decorative text missed a strict image-overlap threshold in an earlier check. Audio can gain volume when identical source sound overlaps during a dissolve. The verification notes tell users to inspect these cases rather than reading a successful encode as proof that the edit looks and sounds right.
Public source does not settle the rights
The root license allows viewing, cloning, study and modification for personal, noncommercial purposes. It forbids paid products, client work, revenue-generating use and business operations without written authorization. It also prohibits republishing the repository or a derivative as a public skill pack, marketplace item, course asset or internal company toolkit. Under the Open Source Definition, an open-source license cannot bar business use or restrict a field of endeavor. Jianying Headless is source-available under a custom license, despite being a repository story in MrKeyoor's open-source section.
The code has several additional rights layers. Its third-party notices credit pyJianYingDraft under Apache 2.0 and an interface adapted from jy-draftc under MIT. The installed Jianying application supplies the underlying native implementation, while FFmpeg remains an external tool with terms determined by its build. The project says its current engine does not directly import pyJianYingDraft, yet it makes no clean-room claim about the project's history or captured native structures.
A permissive license on one borrowed component does not open the whole package. The project's distribution document explicitly separates its own license from Jianying's user agreement, material rights and account entitlements. A cached effect may render correctly while remaining unavailable for commercial use. Technical success cannot answer that licensing question.
What the 603-star burst says
GitHub stars record attention. They say nothing about successful installs. In this case, the attention gathered around a concrete proposition: give an agent a structured editing plan, let it produce a native timeline, and keep the result editable in the desktop application. The repository has only two commits so far, both from September 15, which leaves outside reviewers with a compact snapshot rather than an incremental development history.
The next useful evidence is already named in the project's own documents: a clean-machine install, a cold reopen of generated drafts, testing across another supported setup and a license state that matches the audience the project wants. Its distribution plan says a wider release would require another provenance review, privacy scan and explicit approval. For now, the star burst measures curiosity. The work that would make Jianying Headless reusable by people outside the author's machine is still listed as unfinished.