@tailor-cms/ce-video-edit
Tailor CMS 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, 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tailor-cms/core-components | AI (dependencies): Same-org dependency within the @tailor-cms scope; consistent with this package's purpose as a Tailor CMS component. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): lodash-es is a well-known utility library; phantom detection likely reflects indirect/build-time usage in this component package. | ai | |
| phantom-deps | phantom-dep:@tailor-cms/cek-common | AI (phantom-deps): Same-org dependency; indirect usage in a monorepo component is expected and not a security concern. | ai | |
| phantom-deps | phantom-dep:@tailor-cms/core-components | AI (phantom-deps): Same-org dependency; indirect usage in a monorepo component is expected and not a security concern. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 2 / 9 | |
| 2.0.0 | 2 / 9 | |
| 0.1.0 | 3 / 7 | |
| 0.0.8 | 3 / 8 | |
| 0.0.7 | 2 / 8 | |
| 0.0.6 | 3 / 8 | |
| 0.0.5 | 3 / 8 | |
| 0.0.4 | 3 / 8 | |
| 0.0.3 | 3 / 8 | |
| 0.0.2 | 3 / 8 | |
| 0.0.1 | 1 / 6 |
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.