@tailor-cms/ce-mux-video-server
Tailor CMS MUX video server 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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Tailor CMS uses automated monorepo CI/CD releasing multiple scoped packages simultaneously; rapid publish is expected and benign for this package. | ai | |
| phantom-deps | phantom-dep:sequelize | AI (phantom-deps): sequelize is a declared runtime dep used in config/type context for this server-side CMS component; not directly imported but legitimately present as a peer/config dependency. | ai | |
| dependencies | unvetted-dep:sequelize | AI (dependencies): sequelize is a well-known, widely-used Node.js ORM; its use in a server-side CMS component is expected and benign. | ai | |
| dependencies | unvetted-dep:@mux/mux-node | AI (dependencies): @mux/mux-node is the official Mux API SDK; entirely appropriate for a Mux video server component. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 6 / 3 | |
| 2.0.0 | 6 / 3 | |
| 1.0.0 | 6 / 3 | |
| 0.0.6 | 4 / 6 | |
| 0.0.1 | 3 / 6 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.