@cometchat/calls-sdk-react-native
Cometchat React Native Calling component for iOS and Android
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Metadata-only regression, no behavioral change vs prior approved version. | ai | |
| dependencies | unvetted-peer-dep:react-native-background-timer | AI (dependencies): Expected peer dep for call-state background handling. | ai | |
| dependencies | unvetted-peer-dep:react-native-callstats | AI (dependencies): Expected peer dep for WebRTC calling SDK. | ai | |
| provenance | publisher-changed | AI (provenance): Change is to GitHub Actions CI publisher, a legitimate automation transition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established SDK with docs homepage; README link dump reflects vendor documentation style, not spam. | ai | |
| source-diff | obfuscated-file:dist/index.mjs | AI (source-diff): Minified SDK bundle; sample confirms legitimate React Native calling SDK code, not obfuscated malware. | ai | |
| npm-metadata | url-dep:@cometchat/calls-lib-webrtc | AI (npm-metadata): URL points to CometChat's own Cloudsmith CDN; proprietary WebRTC lib distributed outside npm registry is expected for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 5.0.2 | 7 / 0 | |
| 5.0.1 | 0 / 0 | |
| 5.0.0 | 0 / 0 | |
| 4.4.1 | 0 / 10 | |
| 4.4.0 | 0 / 10 | |
| 4.3.0 | 0 / 10 | |
| 4.2.2 | 0 / 10 | |
| 4.2.1 | 0 / 10 | |
| 4.2.0 | 0 / 10 | |
| 4.1.1 | 0 / 10 | |
| 4.1.0 | 0 / 10 | |
| 4.0.9 | 0 / 10 | |
| 4.0.8 | 0 / 10 | |
| 4.0.7 | 0 / 10 | |
| 4.0.4 | 0 / 10 | |
| 4.0.3 | 0 / 10 | |
| 4.0.2 | 0 / 10 | |
| 4.0.1 | 0 / 10 | |
| 4.0.0 | 0 / 10 |
v5.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-07-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: honey-cometchat.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
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 (honey-cometchat) than the most recent previously approved version (ritikkaushiknpm) on 2024-04-16, but honey-cometchat 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.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
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 (ritikkaushiknpm) than the most recent previously approved version (jitvar.patil) on 2023-10-16, but ritikkaushiknpm 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.
v4.0.1
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 (ritikkaushiknpm) than the most recent previously approved version (jitvar.patil) on 2023-10-16, but ritikkaushiknpm 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.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.