@tailor-cms/ce-mux-video-edit
Tailor CMS MUX video authoring component
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:srt-webvtt | AI (phantom-deps): Config-referenced; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@mux/upchunk | AI (phantom-deps): Config-referenced; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Config-referenced; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@tailor-cms/cek-common | AI (phantom-deps): Same-org scoped dep; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@tailor-cms/core-components | AI (phantom-deps): Same-org scoped dep; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@tailor-cms/core-components | AI (dependencies): Same org scope (@tailor-cms); a first-party dependency of the Tailor CMS ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Quality signals (no README code, no repo URL, no keywords) are cosmetic issues. Package is a legitimate internal component of the @tailor-cms org with clear author attribution. | ai | |
| dependencies | unvetted-dep:@mux/mux-player | AI (dependencies): @mux/mux-player is the official Mux video player package; expected dependency for a Mux video component. | ai | |
| dependencies | unvetted-dep:@mux/upchunk | AI (dependencies): @mux/upchunk is the official Mux upload chunking library; expected for a Mux video authoring component. | ai | |
| dependencies | unvetted-dep:srt-webvtt | AI (dependencies): srt-webvtt is a subtitle conversion utility; appropriate for a video component handling captions. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 4 / 8 | |
| 2.0.0 | 4 / 8 | |
| 1.0.0 | 4 / 8 | |
| 0.0.6 | 6 / 7 | |
| 0.0.5 | 6 / 7 | |
| 0.0.4 | 6 / 7 | |
| 0.0.3 | 6 / 7 | |
| 0.0.2 | 6 / 7 | |
| 0.0.1 | 6 / 7 |
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.