Eight motion packages, live on public npm
The falsifiable questionIs the 'token-driven Remotion monorepo' a real, installable system — or a private folder with a nice README?
Three of six — the weakest receipt on the ledger, kept here because an honest ledger includes its own thin entries.
Baseline
Motion work usually ships as one-off project code: nothing versioned, nothing another team can npm-install.
Method
FrameFX: a Remotion monorepo split into eight scoped packages — @framefx/core, vectors, text, transitions, fx, studio, layout, recipes — published to the public npm registry under this account.
Measured result
All eight packages verified live on the registry at v0.1.0, published 2026-01-28, maintainer hopeatina. npm install @framefx/core works for anyone.
Where it broke
Every package's repository field points to github.com/framefx/framefx — which does not exist (the username belongs to an unrelated empty account). A dead provenance link on all eight packages, found during this audit and queued for the next publish. v0.1.0 also means: published, not yet adopted.
Updates
- Published to the ledger, dead repository field and all.
Next test
Fix the repository field, publish 0.2.0, and earn R with a runnable example gallery.