* fix(studio-server): no write route touches files other tools run or trust A composition previewed in Studio runs same-origin with the API, and the write rule refused only private paths, node_modules and hidden names. Its script could create, overwrite, rename or delete package.json, lock files, agent instruction files and scripts, which a package manager, build tool or coding agent then runs with the developer's rights. Core now names these files in one predicate, toolTrustedFileKind, read in every spelling a case-insensitive file system or Windows opens. Studio's write rule and the registry installer's target rule both use it, so every write route (PUT, POST, PATCH, DELETE, upload, duplicate-file, file-mutations and gsap-mutations) refuses such a target. Deleting or moving a folder that holds one is refused too. Ordinary composition, stylesheet, script-asset and media writes still succeed. * fix(core): fold look-alike letters before matching files other tools trust A case-insensitive macOS volume opens "AGENTſ.md" (long s) as AGENTS.md and "Makefile" (fi ligature) as Makefile, but lower-casing alone does not map either letter. Project path segments now fold names the way such a volume does: NFKC, upper-then-lower case, and invisible characters dropped. Every rule built on the segments gets the fold. Also: - name JSON, YAML and TOML tool config, compose files, turbo.json, nx.json, pyproject.toml and gulp or grunt files - treat a ~N name as a short name only when it has the 8.3 shape and an extension a trusted file's could shorten to, so take~2.mp4 stays writable - refuse to delete or move a folder holding node_modules or .git, walking it without the listing's ignore rules - report an upload refused by the write rule in `skipped`
@hyperframes/core
Types, parsers, generators, compiler, linter, runtime, and frame adapters for the Hyperframes video framework.
Install
npm install @hyperframes/core
Most users don't need to install core directly — the CLI, producer, and studio packages depend on it internally.
What's inside
| Module | Description |
|---|---|
| Types | TimelineElement, CompositionSpec, Asset, canvas dimensions, defaults |
| Parsers | parseHtml — extract timeline elements from HTML; parseGsapScript — parse GSAP animations |
| Generators | generateHyperframesHtml — produce valid Hyperframes HTML from a composition spec |
| Compiler | compileTimingAttrs — resolve data-start / data-duration into absolute times |
| Linter | lintHyperframeHtml — validate Hyperframes HTML (missing attributes, overlapping tracks, etc.) |
| Runtime | IIFE script injected into the browser — manages seek, media playback, and the window.__hf protocol |
| Frame Adapters | Pluggable animation drivers (GSAP, Lottie, CSS, or custom) |
Generated composition trust
Composition generators require trusted authors for code-bearing inputs. styles and
generateHyperframesStyles preserve authored CSS, which can load external resources.
animations may contain __raw: values that are emitted as JavaScript;
includeScripts: true includes executable timeline code. serializeGsapAnimations
also accepts raw preamble, postamble, and a code-bearing timelineVar. Never fill
these inputs with untrusted data. Attribute encoding and closing-tag containment
are not a sandbox; render untrusted compositions in an appropriately isolated
execution environment and never serve them on a privileged origin.
Text content retains the supported inline-formatting sanitizer contract. The clip parser intentionally flattens inner formatting to text, so parse/generate is not a lossless replacement for editing the source HTML.
Frame Adapters
A frame adapter tells the engine how to seek your animation to a specific frame:
import { createGSAPFrameAdapter } from "@hyperframes/core";
const adapter = createGSAPFrameAdapter({
getTimeline: () => gsap.timeline(),
compositionId: "my-video",
});
Implement FrameAdapter for custom animation runtimes:
import type { FrameAdapter } from "@hyperframes/core";
const myAdapter: FrameAdapter = {
id: "my-adapter",
getDurationFrames: () => 300,
seekFrame: (frame) => {
/* seek your animation */
},
};
Parsing and generating HTML
import { parseHtml, generateHyperframesHtml } from "@hyperframes/core";
const { elements, metadata } = parseHtml(htmlString);
const html = generateHyperframesHtml(spec);
Linting
import { lintHyperframeHtml } from "@hyperframes/core/lint";
const result = lintHyperframeHtml(htmlString);
// result.findings: { severity, message, elementId }[]
Documentation
Full documentation: hyperframes.heygen.com/packages/core
Related packages
@hyperframes/engine— rendering engine that drives the browser@hyperframes/producer— full render pipeline (capture + encode)hyperframes— CLI