@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 — 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 |
|---|---|---|---|---|
| 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 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 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 |
v4.0.23
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.