@cometchat/chat-sdk-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:CometChat.js | AI (source-diff): CometChat.js is a standard webpack bundle; minification is expected for this SDK distribution. | ai | |
| source-diff | net-exec-file:CometChat.js | AI (source-diff): Network calls and dynamic module loading are core SDK functionality in a webpack bundle, not dropper behavior. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() usage is part of webpack's module system internals in the bundled output. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 4.0.27 | 0 / 0 | |
| 4.0.26 | 0 / 0 | |
| 4.0.25 | 0 / 0 | |
| 4.0.24 | 0 / 0 | |
| 4.0.23 | 0 / 0 | |
| 4.0.22 | 4 / 26 | |
| 4.0.21 | 0 / 0 | |
| 4.0.20 | 0 / 0 | |
| 4.0.19 | 0 / 0 | |
| 4.0.18 | 0 / 0 | |
| 4.0.17 | 0 / 0 | |
| 4.0.16 | 0 / 0 | |
| 4.0.15 | 0 / 0 | |
| 4.0.14 | 0 / 0 | |
| 4.0.13 | 0 / 0 | |
| 4.0.12 | 0 / 0 | |
| 4.0.11 | 0 / 0 | |
| 4.0.10 | 0 / 0 | |
| 4.0.9 | 0 / 0 | |
| 4.0.8 | 0 / 0 |
v4.0.27
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 (suraj-cometchat) than the most recent previously approved version (luckyrao) on 2026-07-24, but suraj-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.13
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 (rajdubey) than the most recent previously approved version (mathews_cometchat) on 2025-04-23, but rajdubey 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.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
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 (mathews_cometchat) than the most recent previously approved version (ritikkaushiknpm) on 2024-08-08, but mathews_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.10
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 (mathews_cometchat) than the most recent previously approved version (ritikkaushiknpm) on 2024-07-10, but mathews_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.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.