@remotion/compositor-win32-x64-msvc
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): FFmpeg DLLs are the expected payload for this Remotion compositor platform package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific sub-packages in monorepos routinely lack descriptions, keywords, deps, and have minimal entry points. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 4.0.476 | 0 / 0 | |
| 4.0.475 | 0 / 0 | |
| 4.0.474 | 0 / 0 | |
| 4.0.473 | 0 / 0 | |
| 4.0.472 | 0 / 0 | |
| 4.0.471 | 0 / 0 | |
| 4.0.470 | 0 / 0 | |
| 4.0.469 | 0 / 0 | |
| 4.0.468 | 0 / 0 | |
| 4.0.467 | 0 / 0 | |
| 4.0.466 | 0 / 0 | |
| 4.0.465 | 0 / 0 | |
| 4.0.464 | 0 / 0 | |
| 4.0.463 | 0 / 0 | |
| 4.0.462 | 0 / 0 | |
| 4.0.461 | 0 / 0 | |
| 4.0.460 | 0 / 0 | |
| 4.0.459 | 0 / 0 | |
| 4.0.458 | 0 / 0 | |
| 4.0.457 | 0 / 0 | |
| 4.0.456 | 0 / 0 | |
| 4.0.455 | 0 / 0 | |
| 4.0.454 | 0 / 0 | |
| 4.0.453 | 0 / 0 | |
| 4.0.452 | 0 / 0 | |
| 4.0.451 | 0 / 0 | |
| 4.0.450 | 0 / 0 | |
| 4.0.449 | 0 / 0 | |
| 4.0.448 | 0 / 0 | |
| 4.0.447 | 0 / 0 | |
| 4.0.446 | 0 / 0 | |
| 4.0.445 | 0 / 0 | |
| 4.0.444 | 0 / 0 | |
| 4.0.443 | 0 / 0 | |
| 4.0.442 | 0 / 0 |
v4.0.476
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.475
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.474
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.473
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.472
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.471
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.470
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.469
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.468
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.467
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.466
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.465
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.464
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.463
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.462
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.461
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.460
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.459
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.458
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.457
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.456
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.455
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.454
2 findingsPackage contains compiled binaries that could be backdoors: • avcodec-60.dll • avcodec-61.dll • avdevice-60.dll • avdevice-61.dll • avfilter-10.dll • avfilter-9.dll • avformat-60.dll • avformat-61.dll • avutil-58.dll • avutil-59.dll ... and 14 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.453
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.452
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.451
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.450
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.449
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.448
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.447
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.446
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.445
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.444
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.443
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.442
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.