@remotion/media-utils
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Remotion monorepo consistently publishes without Sigstore provenance; stable false positive for this package. | ai |
Versions (showing 51 of 172)
| Version | Deps | Published |
|---|---|---|
| 4.0.473 | 2 / 3 | |
| 4.0.472 | 2 / 3 | |
| 4.0.471 | 2 / 3 | |
| 4.0.470 | 2 / 3 | |
| 4.0.469 | 2 / 3 | |
| 4.0.468 | 2 / 3 | |
| 4.0.467 | 2 / 3 | |
| 4.0.466 | 2 / 3 | |
| 4.0.465 | 2 / 3 | |
| 4.0.464 | 2 / 3 | |
| 4.0.463 | 2 / 3 | |
| 4.0.462 | 2 / 3 | |
| 4.0.461 | 2 / 3 | |
| 4.0.460 | 2 / 3 | |
| 4.0.459 | 2 / 3 | |
| 4.0.458 | 2 / 3 | |
| 4.0.457 | 2 / 3 | |
| 4.0.456 | 2 / 3 | |
| 4.0.455 | 2 / 3 | |
| 4.0.454 | 2 / 3 | |
| 4.0.453 | 2 / 3 | |
| 4.0.452 | 2 / 3 | |
| 4.0.451 | 2 / 3 | |
| 4.0.450 | 2 / 3 | |
| 4.0.449 | 2 / 3 | |
| 4.0.448 | 2 / 3 | |
| 4.0.447 | 2 / 3 | |
| 4.0.446 | 2 / 3 | |
| 4.0.445 | 2 / 3 | |
| 4.0.444 | 2 / 3 | |
| 4.0.443 | 2 / 3 | |
| 4.0.442 | 2 / 3 | |
| 4.0.441 | 2 / 3 | |
| 4.0.440 | 2 / 3 | |
| 4.0.439 | 2 / 3 | |
| 4.0.438 | 2 / 3 | |
| 4.0.437 | 2 / 3 | |
| 4.0.436 | 4 / 3 | |
| 4.0.435 | 4 / 3 | |
| 4.0.434 | 4 / 3 | |
| 4.0.433 | 4 / 3 | |
| 4.0.432 | 4 / 3 | |
| 4.0.431 | 4 / 3 | |
| 4.0.430 | 4 / 3 | |
| 4.0.429 | 4 / 3 | |
| 4.0.428 | 4 / 3 | |
| 4.0.427 | 4 / 3 | |
| 4.0.426 | 4 / 3 | |
| 4.0.425 | 4 / 3 | |
| 4.0.424 | 4 / 3 | |
| 4.0.423 | 4 / 2 |
v4.0.473
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.472
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.471
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.470
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.469
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.468
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.467
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.466
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.465
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.464
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.463
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.462
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.461
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.460
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.459
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.458
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.457
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.456
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.455
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.454
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.441
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.440
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.439
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.438
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.437
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.436
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.435
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.434
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.433
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.432
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.431
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.430
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.429
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.428
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.427
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.426
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.425
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.424
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.423
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.