Render Remotion videos using Node.js or Bun
78%
Total Score
healthy
A highly active, stable release from a well-backed project is offset by workflow injection risk and weak repository-to-package linkage.
No build attestation or trusted-publisher identity was detected. This reduces release transparency, although the package has a long, highly active release history.
The repository name does not match @remotion/renderer and its README does not mention the package. This may reflect a normal monorepo layout, but it weakens direct package-to-repository transparency.
The repository uses TypeScript, Turbo, npm scripts, and Vite, showing an established build system. No security-scanning tools were detected, leaving a modest transparency gap.
No repository security policy was detected. This is a documentation and disclosure gap, though the active organization and extensive maintenance evidence partly compensate.
All six workflows were analyzed, but all 61 detected action uses are unpinned and a high-confidence template-injection finding appears in changelog.yml. The low-confidence cache-poisoning finding is hygiene-level, and no untrusted checkout or script-injection sink was found.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ws Version 8.21.0 | — | — |
execa Version 5.1.1 | — | — |
remotion Version 4.0.535 | — | — |
source-map Version 0.8.0 | — | — |
@remotion/licensing Version 4.0.535 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.