@webitel/ui-chats
Reusable Webitel Frontend Code for Chats UI
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is confirmed by SLSA provenance attestation; expected for CI/CD automation. | ai | |
| provenance | no-provenance | AI (provenance): Webitel org packages consistently lack provenance; stable false positive for this publisher. | ai | |
| phantom-deps | phantom-dep:autolinker | AI (phantom-deps): Library package; deps referenced in config/build but not directly imported in source is expected pattern. | ai | |
| phantom-deps | phantom-dep:insert-text-at-cursor | AI (phantom-deps): Same config-only reference pattern; stable false positive for this package. | ai |
Versions (showing 63 of 63)
| Version | Deps | Published |
|---|---|---|
| 0.1.37 | 2 / 10 | |
| 0.1.36 | 2 / 10 | |
| 0.1.35 | 2 / 9 | |
| 0.1.34 | 2 / 9 | |
| 0.1.33 | 2 / 9 | |
| 0.1.32 | 2 / 9 | |
| 0.1.31 | 2 / 9 | |
| 0.1.30 | 2 / 9 | |
| 0.1.29 | 2 / 9 | |
| 0.1.28 | 2 / 9 | |
| 0.1.27 | 2 / 9 | |
| 0.1.26 | 2 / 9 | |
| 0.1.25 | 2 / 9 | |
| 0.1.24 | 2 / 9 | |
| 0.1.23 | 2 / 9 | |
| 0.1.22 | 2 / 9 | |
| 0.1.21 | 2 / 9 | |
| 0.1.20 | 2 / 9 | |
| 0.1.19 | 2 / 9 | |
| 0.1.18 | 2 / 9 | |
| 0.1.17 | 2 / 9 | |
| 0.1.16 | 2 / 9 | |
| 0.1.15 | 2 / 9 | |
| 0.1.14 | 2 / 9 | |
| 0.1.13 | 2 / 9 | |
| 0.1.12 | 2 / 9 | |
| 0.1.11 | 2 / 9 | |
| 0.1.10 | 2 / 9 | |
| 0.1.9 | 2 / 9 | |
| 0.1.8 | 2 / 11 | |
| 0.1.7 | 2 / 11 | |
| 0.1.6 | 2 / 11 | |
| 0.1.5 | 2 / 11 | |
| 0.1.4 | 2 / 11 | |
| 0.1.3 | 2 / 11 | |
| 0.1.2 | 2 / 11 | |
| 0.1.1 | 2 / 11 | |
| 0.1.0 | 2 / 11 | |
| 0.0.26 | 4 / 9 | |
| 0.0.25 | 4 / 9 | |
| 0.0.24 | 4 / 9 | |
| 0.0.23 | 4 / 9 | |
| 0.0.22 | 4 / 9 | |
| 0.0.21 | 4 / 9 | |
| 0.0.20 | 4 / 9 | |
| 0.0.19 | 4 / 9 | |
| 0.0.18 | 4 / 9 | |
| 0.0.17 | 4 / 9 | |
| 0.0.16 | 4 / 9 | |
| 0.0.15 | 4 / 9 | |
| 0.0.14 | 4 / 9 | |
| 0.0.13 | 4 / 9 | |
| 0.0.12 | 4 / 9 | |
| 0.0.11 | 4 / 9 | |
| 0.0.10 | 4 / 9 | |
| 0.0.9 | 4 / 9 | |
| 0.0.8 | 4 / 9 | |
| 0.0.7 | 4 / 9 | |
| 0.0.6 | 4 / 9 | |
| 0.0.5 | 4 / 9 | |
| 0.0.4 | 4 / 9 | |
| 0.0.3 | 4 / 9 | |
| 0.0.2 | 4 / 9 |
v0.1.37
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.36
2 findingsThis version was published by a different npm account than previous versions on 2026-05-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.