← Home

@cometchat/calls-sdk-javascript

npm

Cometchat's Javascript SDK for In-app Calling.

14
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

cometchatketanrajdubeyanantgargranjanravi85jitvar.patilhoney-cometchatbirendraprasad.guptamathews_cometchataanshi04luckyraoswapnil-cometchatsuraj-cometchatshagun-cometchatprajwaldhule

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/index.es.js AI (source-diff): Vite/Rollup minified bundle output, not true obfuscation. ai
source-diff net-exec-file:dist/index.es.js AI (source-diff): Bundled SDK code with normal fetch/dynamic import, not a loader. ai
source-diff net-exec-file:dist/index.umd.js AI (source-diff): Same bundle in UMD form; CSS/font loading, not malicious exec. ai
provenance publisher-changed AI (provenance): Publisher moved to GitHub Actions CI, a provenance improvement. ai

Versions (showing 14 of 14)

Version Deps Published
5.0.3 1 / 28
5.0.2 1 / 28
5.0.0 1 / 28
4.2.6 0 / 5
4.2.2 0 / 5
4.2.1 0 / 5
4.2.0 0 / 5
4.1.2 0 / 5
4.1.1 0 / 5
4.1.0 0 / 5
4.0.12 0 / 5
4.0.11 0 / 5
4.0.10 0 / 5
4.0.9 0 / 5

v5.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.2

5 findings
HIGH Publisher changed: honey-cometchat → GitHub Actions (on 2026-07-16) provenance

This 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.

HIGH New obfuscated file: dist/index.es.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/index.es.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/index.umd.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.10

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: ritikkaushiknpm → honey-cometchat (on 2024-08-27, known maintainer) provenance

This version was published by a different npm account (honey-cometchat) than the most recent previously approved version (ritikkaushiknpm) on 2024-08-27, 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.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.