@remotion/studio
APIs for interacting with the Remotion Studio
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@remotion/drag-and-drop | AI (dependencies): First-party sibling package within the same monorepo/release train. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a same-version sibling @remotion/* package from the same monorepo; not a third-party supply-chain risk. | ai | |
| dependencies | unvetted-dep:@remotion/timeline-utils | AI (dependencies): Same Remotion monorepo package, always pinned to matching version; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@remotion/web-renderer | AI (dependencies): Sibling monorepo package, same version pin, legitimate remotion ecosystem. | ai | |
| dependencies | unvetted-dep:@remotion/studio-shared | AI (dependencies): Sibling monorepo package, same version pin, legitimate remotion ecosystem. | ai | |
| dependencies | unvetted-dep:@remotion/renderer | AI (dependencies): Sibling monorepo package, same version pin, legitimate remotion ecosystem. | ai | |
| phantom-deps | phantom-dep:memfs | AI (phantom-deps): Declared dep used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Declared dep used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:open | AI (phantom-deps): Declared dep used indirectly; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@remotion/zod-types | AI (dependencies): Sibling monorepo package, same version pin, legitimate remotion ecosystem. | ai | |
| dependencies | unvetted-dep:@remotion/media-utils | AI (dependencies): Sibling monorepo package, same version pin, legitimate remotion ecosystem. | ai |
Versions (showing 100 of 336)
| Version | Deps | Published |
|---|---|---|
| 4.0.398 | 13 / 5 | |
| 4.0.397 | 13 / 5 | |
| 4.0.396 | 13 / 5 | |
| 4.0.395 | 13 / 5 | |
| 4.0.394 | 13 / 5 | |
| 4.0.393 | 13 / 5 | |
| 4.0.392 | 13 / 5 | |
| 4.0.391 | 13 / 5 | |
| 4.0.390 | 13 / 5 | |
| 4.0.389 | 13 / 5 | |
| 4.0.388 | 13 / 5 | |
| 4.0.387 | 13 / 5 | |
| 4.0.386 | 13 / 5 | |
| 4.0.377 | 13 / 5 | |
| 4.0.376 | 13 / 5 | |
| 4.0.375 | 13 / 5 | |
| 4.0.374 | 13 / 5 | |
| 4.0.373 | 13 / 5 | |
| 4.0.372 | 13 / 5 | |
| 4.0.371 | 13 / 5 | |
| 4.0.310 | 12 / 5 | |
| 4.0.309 | 12 / 5 | |
| 4.0.308 | 12 / 5 | |
| 4.0.305 | 12 / 5 | |
| 4.0.304 | 12 / 5 | |
| 4.0.303 | 12 / 5 | |
| 4.0.302 | 12 / 5 | |
| 4.0.301 | 12 / 5 | |
| 4.0.300 | 12 / 5 | |
| 4.0.298 | 12 / 5 | |
| 4.0.297 | 12 / 5 | |
| 4.0.296 | 12 / 5 | |
| 4.0.295 | 12 / 5 | |
| 4.0.294 | 12 / 5 | |
| 4.0.293 | 12 / 5 | |
| 4.0.292 | 12 / 5 | |
| 4.0.291 | 12 / 5 | |
| 4.0.290 | 12 / 5 | |
| 4.0.289 | 12 / 5 | |
| 4.0.288 | 12 / 5 | |
| 4.0.287 | 12 / 5 | |
| 4.0.286 | 12 / 5 | |
| 4.0.285 | 12 / 5 | |
| 4.0.284 | 12 / 5 | |
| 4.0.282 | 12 / 5 | |
| 4.0.280 | 12 / 5 | |
| 4.0.279 | 12 / 5 | |
| 4.0.278 | 12 / 5 | |
| 4.0.277 | 10 / 7 | |
| 4.0.276 | 10 / 7 | |
| 4.0.275 | 10 / 7 | |
| 4.0.274 | 10 / 7 | |
| 4.0.273 | 10 / 7 | |
| 4.0.272 | 10 / 7 | |
| 4.0.271 | 10 / 7 | |
| 4.0.270 | 10 / 7 | |
| 4.0.269 | 10 / 7 | |
| 4.0.268 | 10 / 7 | |
| 4.0.267 | 10 / 7 | |
| 4.0.266 | 10 / 7 | |
| 4.0.265 | 10 / 7 | |
| 4.0.264 | 10 / 7 | |
| 4.0.263 | 10 / 7 | |
| 4.0.262 | 10 / 7 | |
| 4.0.261 | 10 / 7 | |
| 4.0.260 | 10 / 7 | |
| 4.0.259 | 10 / 7 | |
| 4.0.258 | 10 / 7 | |
| 4.0.257 | 10 / 7 | |
| 4.0.256 | 10 / 7 | |
| 4.0.255 | 10 / 7 | |
| 4.0.254 | 10 / 7 | |
| 4.0.253 | 10 / 7 | |
| 4.0.252 | 10 / 7 | |
| 4.0.251 | 10 / 7 | |
| 4.0.250 | 10 / 7 | |
| 4.0.249 | 10 / 7 | |
| 4.0.248 | 10 / 7 | |
| 4.0.247 | 10 / 7 | |
| 4.0.246 | 10 / 7 | |
| 4.0.245 | 10 / 7 | |
| 4.0.244 | 10 / 7 | |
| 4.0.243 | 10 / 7 | |
| 4.0.242 | 10 / 7 | |
| 4.0.241 | 9 / 7 | |
| 4.0.240 | 9 / 7 | |
| 4.0.239 | 9 / 7 | |
| 4.0.237 | 9 / 7 | |
| 4.0.236 | 9 / 7 | |
| 4.0.235 | 9 / 7 | |
| 4.0.234 | 9 / 7 | |
| 4.0.233 | 9 / 7 | |
| 4.0.232 | 9 / 7 | |
| 4.0.231 | 9 / 7 | |
| 4.0.230 | 9 / 7 | |
| 4.0.229 | 9 / 7 | |
| 4.0.228 | 9 / 7 | |
| 4.0.227 | 9 / 7 | |
| 4.0.226 | 9 / 5 | |
| 4.0.225 | 9 / 5 |
v4.0.398
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.397
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.396
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.395
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.394
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.393
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.392
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.391
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.390
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.389
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.388
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.387
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.386
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.377
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.376
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.375
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.374
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.373
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.372
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.371
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.291
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.290
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.289
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.288
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.287
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.286
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.285
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.284
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.282
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.280
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.279
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.278
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.277
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.276
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.275
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.274
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.273
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.272
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.271
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.270
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.269
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.268
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.267
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.266
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.265
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.264
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.263
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.262
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.261
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.260
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.259
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.258
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.257
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.256
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.255
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.254
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.253
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.252
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.251
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.250
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.249
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.248
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.247
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.246
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.245
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.244
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.243
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.242
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.241
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.240
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.239
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.237
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.234
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.233
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.231
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.