CodeVetter · Repo Unpack · Risk map
motiondivision/motion
The observations below identify sensitive boundaries and change hotspots, not confirmed vulnerabilities. Release scripts have filesystem and network effects outside the animation runtime. Animation correctness depends on browser capability detection, shared rendering ownership, lifecycle ordering, and bundle/context identity. Two retention and CSP concerns are explicitly labeled hypotheses requiring targeted verification.
- Release commands have substantial side effects: new invokes Lerna publication and site mirroring, postpublish pushes tags, and Makefile clean removes node_modules and invokes git clean -fdX.
- pushToSite copies a file outside this checkout into an environment-selected MOTION_API_PATH or ~/Sites/motion-api; it checks destination existence but the source does not constrain the destination to this repository.
- notifySlack loads dotenv, accepts an overridable SLACK_UPDATE_API_URL, and sends UPDATE_SECRET_TOKEN as a bearer header; production requires a token, while development permits a test token and local HTTP.
- The Claude workflow executes on @claude-bearing issue/comment/review content, requests id-token write permission, and delegates to a version-tagged third-party action using an OAuth-secret reference; authorization beyond the visible condition is outside this source inspection.
- Hypothesis: the module-level timelineCache can retain detached containers and targets because it uses nested Maps with no eviction in get-timeline.ts; listener cleanup in attachToAnimation does not remove those cache entries. (inferred)
- Hypothesis: strict CSP may block view-transition CSS because css.commit creates and appends a style element without assigning a nonce, despite MotionConfig exposing a nonce option. Browser verification is needed to establish impact. (inferred)
- Bundling and public export shape are compatibility hotspots: shared CommonJS contexts are required for LazyMotion/m communication, and motion/react deliberately avoids a duplicate-source re-export pattern documented as causing Turbopack OOM.
- Projection and keyframe measurement change live DOM state: projection cancels optimized transforms before snapshots, resets transforms before measuring nodes, and keyframe resolution temporarily renders styles and restores scroll position. Frame-order changes therefore cross multiple rendering responsibilities.