@cometchat/chat-uikit-react-native
Ready-to-use Chat UI Components for React Native
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established CometChat package; lack of provenance is consistent across all prior versions and is not a risk signal here. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types is a declared runtime dep used by convention in React Native packages; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/prop-types | AI (phantom-deps): Type-only package loaded by convention; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.3.6 | 7 / 13 | |
| 5.3.4 | 6 / 13 | |
| 5.2.7 | 6 / 13 | |
| 5.2.5 | 6 / 13 | |
| 5.0.2 | 2 / 13 |
v5.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.