@remotion/compositor-linux-x64-gnu
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): Platform-specific binary shard for Remotion; ffmpeg/ffprobe/remotion binaries are the intended payload. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Empty index.js and no deps are expected for a native binary shard package. | ai |
Versions (showing 28 of 128)
| Version | Deps | Published |
|---|---|---|
| 4.0.399 | 0 / 0 | |
| 4.0.398 | 0 / 0 | |
| 4.0.397 | 0 / 0 | |
| 4.0.396 | 0 / 0 | |
| 4.0.395 | 0 / 0 | |
| 4.0.394 | 0 / 0 | |
| 4.0.393 | 0 / 0 | |
| 4.0.392 | 0 / 0 | |
| 4.0.391 | 0 / 0 | |
| 4.0.390 | 0 / 0 | |
| 4.0.388 | 0 / 0 | |
| 4.0.387 | 0 / 0 | |
| 4.0.386 | 0 / 0 | |
| 4.0.385 | 0 / 0 | |
| 4.0.384 | 0 / 0 | |
| 4.0.383 | 0 / 0 | |
| 4.0.382 | 0 / 0 | |
| 4.0.381 | 0 / 0 | |
| 4.0.380 | 0 / 0 | |
| 4.0.379 | 0 / 0 | |
| 4.0.378 | 0 / 0 | |
| 4.0.377 | 0 / 0 | |
| 4.0.376 | 0 / 0 | |
| 4.0.375 | 0 / 0 | |
| 4.0.374 | 0 / 0 | |
| 4.0.373 | 0 / 0 | |
| 4.0.372 | 0 / 0 | |
| 4.0.371 | 0 / 0 |
v4.0.399
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.398
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.397
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.396
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.395
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.394
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.393
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.392
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.391
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.390
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.388
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.387
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.386
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.385
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.384
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.383
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.382
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.381
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.380
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.379
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.378
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.377
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.376
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.375
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.374
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.373
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.372
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.371
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.