@retailcrm/embed-ui-v1-contexts
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:@floating-ui/dom | AI (phantom-deps): Declared as runtime dep; used transitively or in config — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@floating-ui/core | AI (phantom-deps): Declared as runtime dep; used transitively or in config — stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established RetailCRM org package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 66 of 66)
| Version | Deps | Published |
|---|---|---|
| 0.9.29 | 3 / 8 | |
| 0.9.28 | 3 / 8 | |
| 0.9.27 | 3 / 8 | |
| 0.9.26 | 3 / 8 | |
| 0.9.25 | 3 / 8 | |
| 0.9.24 | 3 / 8 | |
| 0.9.23 | 3 / 8 | |
| 0.9.22 | 2 / 8 | |
| 0.9.21 | 2 / 8 | |
| 0.9.19 | 2 / 8 | |
| 0.9.18 | 2 / 8 | |
| 0.9.17 | 2 / 8 | |
| 0.9.16 | 2 / 8 | |
| 0.9.15 | 2 / 8 | |
| 0.9.14 | 2 / 8 | |
| 0.9.13 | 2 / 8 | |
| 0.9.12 | 2 / 8 | |
| 0.9.11 | 2 / 8 | |
| 0.9.10 | 4 / 8 | |
| 0.9.9 | 4 / 8 | |
| 0.9.8 | 4 / 8 | |
| 0.9.7 | 4 / 8 | |
| 0.9.6 | 4 / 8 | |
| 0.9.5 | 4 / 6 | |
| 0.9.4 | 4 / 6 | |
| 0.9.3 | 4 / 6 | |
| 0.9.2 | 4 / 6 | |
| 0.9.1 | 4 / 6 | |
| 0.9.0 | 4 / 6 | |
| 0.8.4 | 4 / 6 | |
| 0.8.3 | 4 / 6 | |
| 0.8.2 | 4 / 6 | |
| 0.8.1 | 4 / 6 | |
| 0.8.0 | 4 / 6 | |
| 0.7.0 | 4 / 6 | |
| 0.6.1 | 4 / 6 | |
| 0.6.0 | 4 / 6 | |
| 0.5.22 | 4 / 6 | |
| 0.5.21 | 2 / 6 | |
| 0.5.20 | 2 / 6 | |
| 0.5.19 | 2 / 6 | |
| 0.5.18 | 2 / 6 | |
| 0.5.17 | 2 / 6 | |
| 0.5.16 | 2 / 6 | |
| 0.5.15 | 2 / 6 | |
| 0.5.14 | 2 / 6 | |
| 0.5.13 | 2 / 6 | |
| 0.5.12 | 2 / 6 | |
| 0.5.11 | 1 / 6 | |
| 0.5.10 | 1 / 6 | |
| 0.5.9 | 1 / 6 | |
| 0.5.8 | 1 / 6 | |
| 0.5.7 | 1 / 6 | |
| 0.5.6 | 1 / 6 | |
| 0.5.5 | 1 / 6 | |
| 0.5.4 | 1 / 6 | |
| 0.5.3 | 1 / 6 | |
| 0.5.2 | 1 / 6 | |
| 0.5.1 | 1 / 6 | |
| 0.5.0 | 1 / 6 | |
| 0.4.9 | 1 / 6 | |
| 0.4.8 | 1 / 6 | |
| 0.4.7 | 1 / 6 | |
| 0.4.6 | 1 / 6 | |
| 0.4.5 | 2 / 5 | |
| 0.4.4 | 2 / 5 |
v0.5.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.