@tailor-cms/ce-single-choice-display
Tailor CMS single choice end-user 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 dependency in package.json; phantom detection reflects indirect/transitive usage pattern typical for this type of component package. | ai | |
| phantom-deps | phantom-dep:@tailor-cms/lx-components | AI (phantom-deps): Same-org dependency declared in package.json; phantom detection reflects indirect usage pattern consistent with this CMS component package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 1 / 9 | |
| 2.0.0 | 1 / 9 | |
| 0.1.0 | 2 / 7 | |
| 0.0.21 | 1 / 6 | |
| 0.0.20 | 1 / 6 | |
| 0.0.19 | 1 / 6 | |
| 0.0.18 | 1 / 6 | |
| 0.0.17 | 1 / 6 | |
| 0.0.16 | 1 / 6 | |
| 0.0.15 | 1 / 6 | |
| 0.0.14 | 1 / 6 | |
| 0.0.13 | 1 / 6 | |
| 0.0.12 | 1 / 6 | |
| 0.0.11 | 1 / 6 | |
| 0.0.10 | 1 / 6 | |
| 0.0.9 | 1 / 6 | |
| 0.0.8 | 1 / 6 | |
| 0.0.7 | 1 / 6 | |
| 0.0.5 | 0 / 6 | |
| 0.0.4 | 0 / 6 | |
| 0.0.3 | 0 / 6 | |
| 0.0.2 | 0 / 6 | |
| 0.0.1 | 0 / 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.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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. 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.