@tailor-cms/ce-image-edit
Tailor CMS image 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): Direct dependency; used in TypeScript types and build config. | ai | |
| phantom-deps | phantom-dep:@tailor-cms/cek-common | AI (phantom-deps): Same-org internal dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@tailor-cms/core-components | AI (phantom-deps): Same-org internal dependency; stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal component; minimal public docs expected for org-internal packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 1 / 8 | |
| 2.0.1 | 1 / 8 | |
| 2.0.0 | 1 / 8 | |
| 1.1.0 | 3 / 7 | |
| 1.0.4 | 3 / 7 | |
| 1.0.3 | 3 / 7 | |
| 1.0.2 | 2 / 7 | |
| 1.0.1 | 3 / 7 | |
| 1.0.0 | 1 / 6 |
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.