@remotion/svg-3d-engine
3D SVG extrusion effects
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Remotion monorepo packages consistently lack Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 51 of 241)
| Version | Deps | Published |
|---|---|---|
| 4.0.500 | 1 / 3 | |
| 4.0.499 | 1 / 3 | |
| 4.0.498 | 1 / 3 | |
| 4.0.497 | 1 / 3 | |
| 4.0.496 | 1 / 3 | |
| 4.0.495 | 1 / 3 | |
| 4.0.494 | 1 / 3 | |
| 4.0.493 | 1 / 3 | |
| 4.0.492 | 1 / 3 | |
| 4.0.491 | 1 / 3 | |
| 4.0.490 | 1 / 3 | |
| 4.0.489 | 1 / 3 | |
| 4.0.488 | 1 / 3 | |
| 4.0.487 | 1 / 3 | |
| 4.0.486 | 1 / 3 | |
| 4.0.485 | 1 / 3 | |
| 4.0.484 | 1 / 3 | |
| 4.0.483 | 1 / 3 | |
| 4.0.482 | 1 / 3 | |
| 4.0.481 | 1 / 3 | |
| 4.0.479 | 1 / 3 | |
| 4.0.478 | 1 / 3 | |
| 4.0.477 | 1 / 3 | |
| 4.0.476 | 1 / 3 | |
| 4.0.475 | 1 / 3 | |
| 4.0.474 | 1 / 3 | |
| 4.0.473 | 1 / 3 | |
| 4.0.472 | 1 / 3 | |
| 4.0.471 | 1 / 3 | |
| 4.0.470 | 1 / 3 | |
| 4.0.469 | 1 / 3 | |
| 4.0.468 | 1 / 3 | |
| 4.0.467 | 1 / 3 | |
| 4.0.466 | 1 / 3 | |
| 4.0.465 | 1 / 3 | |
| 4.0.464 | 1 / 3 | |
| 4.0.463 | 1 / 3 | |
| 4.0.462 | 1 / 3 | |
| 4.0.461 | 1 / 3 | |
| 4.0.460 | 1 / 3 | |
| 4.0.459 | 1 / 3 | |
| 4.0.458 | 1 / 3 | |
| 4.0.457 | 1 / 3 | |
| 4.0.456 | 1 / 3 | |
| 4.0.455 | 1 / 3 | |
| 4.0.454 | 1 / 3 | |
| 4.0.453 | 1 / 3 | |
| 4.0.452 | 1 / 3 | |
| 4.0.451 | 1 / 3 | |
| 4.0.450 | 1 / 3 | |
| 4.0.449 | 1 / 3 |
v4.0.500
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.499
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.498
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.497
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.496
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.495
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.494
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.493
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.492
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.491
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.490
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.489
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.488
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.487
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.486
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.485
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.