@tailor-cms/ce-pdf-edit
Tailor CMS PDF element 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): lodash-es is a declared runtime dep in a Vue component library; indirect usage via build tooling is expected and not a security concern. | ai | |
| phantom-deps | phantom-dep:@tailor-cms/cek-common | AI (phantom-deps): Same-org dependency; indirect import pattern is normal for this monorepo-style package structure. | ai | |
| phantom-deps | phantom-dep:@tailor-cms/core-components | AI (phantom-deps): Same-org dependency; indirect import pattern is normal for this monorepo-style package structure. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 1 / 8 | |
| 2.0.0 | 1 / 8 | |
| 0.1.0 | 3 / 7 | |
| 0.0.8 | 3 / 7 | |
| 0.0.7 | 2 / 7 | |
| 0.0.6 | 3 / 7 | |
| 0.0.5 | 2 / 7 | |
| 0.0.4 | 2 / 7 | |
| 0.0.3 | 2 / 7 | |
| 0.0.2 | 2 / 7 | |
| 0.0.1 | 2 / 7 |
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.