@retailcrm/embed-ui
API and components for creating RetailCRM UI extensions
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:bin/embed-ui.mjs | AI (source-diff): Bundled CLI binary built with Vite; long lines are minified bundle output, not obfuscation. Code is readable and benign. | ai | |
| provenance | no-provenance | AI (provenance): Established retailcrm publisher with long track record; lack of Sigstore attestation is not a disqualifier here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate SDK package for RetailCRM UI extensions; sparse README/keywords are a style choice, not spam. | ai | |
| phantom-deps | phantom-dep:@floating-ui/dom | AI (phantom-deps): Declared as runtime dep and referenced in config; phantom-dep heuristic fires due to indirect import pattern in this build. | ai | |
| phantom-deps | phantom-dep:@floating-ui/core | AI (phantom-deps): Same as @floating-ui/dom — declared dep, config-referenced, stable false positive for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.9.28 | 11 / 38 | |
| 0.9.27 | 11 / 38 | |
| 0.9.26 | 11 / 38 | |
| 0.9.25 | 11 / 38 | |
| 0.9.24 | 11 / 38 | |
| 0.9.23 | 11 / 38 | |
| 0.9.22 | 11 / 38 | |
| 0.9.21 | 8 / 39 | |
| 0.9.19 | 8 / 38 | |
| 0.9.18 | 8 / 38 | |
| 0.9.17 | 8 / 38 | |
| 0.9.16 | 8 / 38 | |
| 0.9.15 | 8 / 38 | |
| 0.9.14 | 8 / 38 | |
| 0.9.12 | 8 / 38 | |
| 0.9.10 | 7 / 37 | |
| 0.9.8 | 7 / 36 | |
| 0.9.7 | 7 / 36 | |
| 0.9.6 | 7 / 36 | |
| 0.9.5 | 7 / 36 | |
| 0.9.3 | 7 / 36 | |
| 0.9.2 | 7 / 36 | |
| 0.8.3 | 7 / 36 | |
| 0.8.1 | 7 / 36 | |
| 0.8.0 | 7 / 36 | |
| 0.7.0 | 7 / 36 | |
| 0.6.1 | 7 / 36 | |
| 0.6.0 | 7 / 36 |
v0.9.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.24
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.23
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.22
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.