← Home

@cometchat/chat-uikit-angular

npm Repository Homepage

Ready-to-use Chat UI Components for Angular (JavaScript/Web)

10
Versions
https://www.cometchat.com/legal-terms-of-service
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

CometChatchatmessagingchatuikitpromessageuikitmessaginguikitaudiochatvideochatwebRTCAngular

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:fesm2022/cometchat-chat-uikit-angular.mjs AI (source-diff): Standard Angular FESM2022 bundle; long lines are normal for bundled output, not obfuscation. ai
source-diff obfuscated-file:types/cometchat-chat-uikit-angular.d.ts AI (source-diff): TypeScript declaration file with long lines from concatenated type exports; not obfuscated. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a well-known Angular/TypeScript runtime helper; implicit usage is expected. ai

Versions (showing 10 of 10)

Version Deps Published
5.1.0 1 / 0
5.0.4 1 / 0
5.0.3 1 / 0
5.0.2 1 / 0
5.0.1 1 / 0
5.0.0 1 / 0
4.3.36 1 / 0
4.3.35 1 / 0
4.3.34 1 / 0
4.3.33 1 / 0

v5.1.0

1 finding
LOW No provenance attestation provenance

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

v5.0.4

1 finding
LOW No provenance attestation provenance

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

v4.3.35

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: prajwaldhule → rajdubey (on 2025-12-16, known maintainer) provenance

This version was published by a different npm account (rajdubey) than the most recent previously approved version (prajwaldhule) on 2025-12-16, 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.3.34

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

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.