@remotion/compositor-linux-x64-musl
Linux x64 binary for the Remotion Rust code
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Remotion compositor packages intentionally ship prebuilt FFmpeg and Rust binaries per platform; stable pattern across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific binary distribution package; no deps, empty index.js, and no keywords are expected for this package type. | ai |
Versions (showing 51 of 127)
| Version | Deps | Published |
|---|---|---|
| 4.0.499 | 0 / 0 | |
| 4.0.498 | 0 / 0 | |
| 4.0.497 | 0 / 0 | |
| 4.0.496 | 0 / 0 | |
| 4.0.495 | 0 / 0 | |
| 4.0.494 | 0 / 0 | |
| 4.0.493 | 0 / 0 | |
| 4.0.492 | 0 / 0 | |
| 4.0.491 | 0 / 0 | |
| 4.0.490 | 0 / 0 | |
| 4.0.489 | 0 / 0 | |
| 4.0.488 | 0 / 0 | |
| 4.0.487 | 0 / 0 | |
| 4.0.486 | 0 / 0 | |
| 4.0.485 | 0 / 0 | |
| 4.0.484 | 0 / 0 | |
| 4.0.483 | 0 / 0 | |
| 4.0.482 | 0 / 0 | |
| 4.0.481 | 0 / 0 | |
| 4.0.479 | 0 / 0 | |
| 4.0.478 | 0 / 0 | |
| 4.0.477 | 0 / 0 | |
| 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 |
v4.0.499
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.498
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.497
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.496
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.495
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.494
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.493
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.492
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.491
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.490
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.489
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.488
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.487
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.486
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.485
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.484
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.