@wildix/xbees-conversations-utils
This package wraps a `StreamChat` client into a proxy that adds shared rate-limit protection around Stream SDK calls without changing the normal sync API contract. Async calls go through retry / cooldown handling, while sync methods stay sync. If a proxie
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal @wildix scoped utility; sparse metadata is a consistent pattern across its 100 published versions, not a spam indicator. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used inside a Proxy handler for rate-limited stream proxying — idiomatic JS pattern, not obfuscation. | ai |
Versions (showing 100 of 104)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 2 / 8 | |
| 2.0.1 | 3 / 7 | |
| 2.0.0 | 3 / 9 | |
| 1.3.1 | 3 / 9 | |
| 1.3.0 | 5 / 9 | |
| 1.2.10 | 5 / 9 | |
| 1.2.9 | 5 / 9 | |
| 1.2.8 | 5 / 9 | |
| 1.2.7 | 5 / 9 | |
| 1.2.6 | 5 / 9 | |
| 1.2.5 | 6 / 9 | |
| 1.2.4 | 5 / 8 | |
| 1.2.3 | 5 / 8 | |
| 1.2.2 | 5 / 8 | |
| 1.2.1 | 5 / 8 | |
| 1.2.0 | 5 / 8 | |
| 1.1.93 | 5 / 8 | |
| 1.1.92 | 5 / 8 | |
| 1.1.91 | 5 / 8 | |
| 1.1.90 | 5 / 8 | |
| 1.1.89 | 5 / 8 | |
| 1.1.88 | 5 / 8 | |
| 1.1.87 | 5 / 8 | |
| 1.1.86 | 5 / 8 | |
| 1.1.85 | 5 / 8 | |
| 1.1.84 | 3 / 6 | |
| 1.1.83 | 3 / 6 | |
| 1.1.81 | 5 / 8 | |
| 1.1.80 | 5 / 8 | |
| 1.1.79 | 5 / 8 | |
| 1.1.78 | 5 / 8 | |
| 1.1.77 | 5 / 8 | |
| 1.1.76 | 5 / 8 | |
| 1.1.75 | 5 / 8 | |
| 1.1.74 | 5 / 8 | |
| 1.1.73 | 5 / 8 | |
| 1.1.72 | 5 / 8 | |
| 1.1.71 | 5 / 8 | |
| 1.1.70 | 5 / 8 | |
| 1.1.69 | 5 / 8 | |
| 1.1.68 | 5 / 8 | |
| 1.1.67 | 5 / 8 | |
| 1.1.66 | 5 / 8 | |
| 1.1.65 | 5 / 8 | |
| 1.1.64 | 5 / 8 | |
| 1.1.63 | 5 / 8 | |
| 1.1.62 | 5 / 8 | |
| 1.1.61 | 5 / 8 | |
| 1.1.60 | 5 / 8 | |
| 1.1.59 | 5 / 8 | |
| 1.1.58 | 5 / 8 | |
| 1.1.57 | 5 / 6 | |
| 1.1.56 | 5 / 6 | |
| 1.1.55 | 3 / 6 | |
| 1.1.54 | 3 / 6 | |
| 1.1.53 | 3 / 6 | |
| 1.1.52 | 3 / 6 | |
| 1.1.51 | 3 / 6 | |
| 1.1.50 | 3 / 6 | |
| 1.1.49 | 3 / 6 | |
| 1.1.48 | 3 / 6 | |
| 1.1.47 | 3 / 6 | |
| 1.1.46 | 3 / 6 | |
| 1.1.45 | 3 / 6 | |
| 1.1.44 | 3 / 6 | |
| 1.1.43 | 3 / 6 | |
| 1.1.42 | 3 / 6 | |
| 1.1.41 | 3 / 6 | |
| 1.1.4 | 3 / 6 | |
| 1.1.3 | 3 / 6 | |
| 1.1.2 | 3 / 6 | |
| 1.1.1 | 3 / 6 | |
| 1.1.0 | 3 / 6 | |
| 1.0.31 | 3 / 6 | |
| 1.0.30 | 3 / 6 | |
| 1.0.29 | 3 / 6 | |
| 1.0.28 | 3 / 6 | |
| 1.0.27 | 3 / 6 | |
| 1.0.26 | 3 / 6 | |
| 1.0.25 | 3 / 6 | |
| 1.0.24 | 3 / 6 | |
| 1.0.23 | 3 / 6 | |
| 1.0.22 | 3 / 5 | |
| 1.0.21 | 3 / 5 | |
| 1.0.20 | 3 / 5 | |
| 1.0.19 | 3 / 5 | |
| 1.0.18 | 3 / 5 | |
| 1.0.17 | 3 / 5 | |
| 1.0.16 | 3 / 5 | |
| 1.0.15 | 3 / 5 | |
| 1.0.14 | 3 / 5 | |
| 1.0.13 | 3 / 5 | |
| 1.0.12 | 3 / 5 | |
| 1.0.11 | 3 / 5 | |
| 1.0.10 | 3 / 5 | |
| 1.0.9 | 3 / 5 | |
| 1.0.8 | 3 / 5 | |
| 1.0.7 | 3 / 5 | |
| 1.0.6 | 3 / 5 | |
| 1.0.5 | 3 / 5 |
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vruban.wildix) than the most recent previously approved version (mike.lozinsky) on 2026-07-02, but vruban.wildix is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.