Render videos in the browser
78%
Total Score
healthy
An active organization-backed project ships frequently, but its workflow audit found a high-confidence template-injection issue and broadly unpinned actions.
No build attestation or trusted-publisher provenance is present, leaving publication origin less independently verifiable despite the active source project.
The repository name does not match the package and its README does not mention @remotion/web-renderer, creating a package-to-source traceability concern even though a monorepo can legitimately contain subpackages.
The project uses TypeScript, Turbo, npm scripts, and Vite, but no security-scanning tools were detected, leaving a modest hygiene gap.
The repository has no security policy, reducing transparency for vulnerability reporting and response expectations.
All six workflows were analyzed, but one high-confidence template-injection finding warrants caution. All 61 detected action references are unpinned, while the low-confidence cache-poisoning finding is hygiene-level and the pull_request_target trigger has no untrusted checkout or script-injection sink.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
remotion Version 4.0.535 | — | — |
mediabunny Version 1.61.3 | — | — |
@remotion/licensing Version 4.0.535 | — | — |
@mediabunny/aac-encoder Version 1.61.3 | — | — |
@mediabunny/mp3-encoder Version 1.61.3 | — | — |
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.