← Home

@cometchat/chat-sdk-javascript

npm Repository Homepage
23
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

Keywords

CometChatchatmessagingchatsdkpromessagesdkmessagingsdkaudiochatvideochatwebRTC

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): All new maintainers have cometchat-aligned usernames; consistent with org-level maintainer expansion. ai
semgrep semgrep:new-function-constructor AI (semgrep): Fires in minified bundle entry point; standard pattern for bundled SDKs, not a dynamic code injection risk. ai
bogus-package bogus-package AI (bogus-package): No-deps and link-dump README are expected for a self-contained bundled SDK; not spam indicators here. ai

Versions (showing 23 of 23)

Version Deps Published
4.1.13 0 / 0
4.1.12 0 / 0
4.1.11 0 / 0
4.1.10 0 / 0
4.1.9 0 / 0
4.1.8 0 / 0
4.1.7 0 / 0
4.1.6 0 / 0
4.1.5 0 / 0
4.1.4 0 / 0
4.1.3 0 / 0
4.1.2 0 / 0
4.1.1 0 / 0
4.1.0 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
4.0.7 0 / 0
4.0.6 0 / 0

v4.1.13

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: aanshi04 → prajwaldhule (on 2026-07-25, known maintainer) provenance

This version was published by a different npm account (prajwaldhule) than the most recent previously approved version (aanshi04) on 2026-07-25, but prajwaldhule 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.1.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.12

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: mathews_cometchat → rajdubey (on 2025-04-23, known maintainer) provenance

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

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: mathews_cometchat → rajdubey (on 2025-04-02, known maintainer) provenance

This version was published by a different npm account (rajdubey) than the most recent previously approved version (mathews_cometchat) on 2025-04-02, 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.10

1 finding
LOW No provenance attestation provenance

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

v4.0.9

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 → mathews_cometchat (on 2024-08-08, known maintainer) provenance

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

1 finding
LOW No provenance attestation provenance

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

v4.0.7

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.

v4.0.6

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.