@twick/studio
`@twick/studio` is a high‑level React package that composes the core Twick building blocks (timeline, canvas, live‑player, video‑editor) into a ready‑to‑use editor UI.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a peer dep used via config/bundler; stable false positive for this React component package. | ai | |
| phantom-deps | phantom-dep:@twick/live-player | AI (phantom-deps): Same-org scope dep likely re-exported or used transitively; stable for this package. | ai | |
| phantom-deps | phantom-dep:@twick/media-utils | AI (phantom-deps): Same-org scope dep likely re-exported or used transitively; stable for this package. | ai | |
| phantom-deps | phantom-dep:@twick/visualizer | AI (phantom-deps): Same-org scope dep; likely re-exported or used transitively in monorepo. | ai | |
| phantom-deps | phantom-dep:@twick/core | AI (phantom-deps): Same-org scope dep; likely re-exported or used transitively in monorepo. | ai | |
| phantom-deps | phantom-dep:lucide-react | AI (phantom-deps): Icon library referenced in config/re-exported; stable false positive. | ai | |
| phantom-deps | phantom-dep:@twick/player-react | AI (phantom-deps): Same-org scope dep; likely re-exported or used transitively in monorepo. | ai | |
| phantom-deps | phantom-dep:@twick/canvas | AI (phantom-deps): Same-org scope dep; likely re-exported or used transitively in monorepo. | ai | |
| phantom-deps | phantom-dep:@twick/workflow | AI (phantom-deps): Same-org scope dep; likely re-exported or used transitively in monorepo. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 0.15.30 | 12 / 14 | |
| 0.15.29 | 12 / 14 | |
| 0.15.28 | 12 / 14 | |
| 0.15.27 | 12 / 14 | |
| 0.15.26 | 12 / 14 | |
| 0.15.25 | 12 / 14 | |
| 0.15.24 | 12 / 14 | |
| 0.15.23 | 11 / 14 | |
| 0.15.20 | 10 / 14 | |
| 0.15.19 | 9 / 14 | |
| 0.15.18 | 9 / 14 | |
| 0.15.16 | 9 / 14 | |
| 0.15.15 | 9 / 14 | |
| 0.15.14 | 9 / 12 | |
| 0.15.13 | 9 / 12 | |
| 0.15.12 | 9 / 12 | |
| 0.15.11 | 9 / 12 | |
| 0.15.10 | 9 / 12 | |
| 0.15.9 | 9 / 12 | |
| 0.15.8 | 9 / 12 | |
| 0.15.7 | 9 / 12 | |
| 0.15.6 | 9 / 12 | |
| 0.15.5 | 9 / 12 | |
| 0.15.4 | 9 / 12 | |
| 0.15.3 | 9 / 12 | |
| 0.15.2 | 9 / 12 | |
| 0.15.1 | 5 / 12 | |
| 0.15.0 | 5 / 12 | |
| 0.14.20 | 7 / 12 | |
| 0.14.18 | 3 / 12 | |
| 0.14.17 | 3 / 12 | |
| 0.14.16 | 3 / 12 | |
| 0.14.15 | 3 / 12 | |
| 0.14.14 | 3 / 12 | |
| 0.14.13 | 3 / 12 | |
| 0.14.12 | 3 / 12 | |
| 0.14.11 | 3 / 12 | |
| 0.14.10 | 3 / 12 | |
| 0.14.9 | 3 / 12 | |
| 0.14.8 | 3 / 12 | |
| 0.14.7 | 3 / 11 | |
| 0.14.6 | 3 / 11 | |
| 0.14.5 | 3 / 13 |
v0.15.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.