@cometchat/chat-uikit-react-native
Ready-to-use Chat UI Components for 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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publisher has long clean history; likely CI config drift, not compromise. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Same cause: comparing across skipped versions inflates new-file count. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Diff baseline is a newer sibling version; size growth reflects bundled audio/sourcemap assets. | ai | |
| provenance | publisher-changed | AI (provenance): New publisher is a vetted CometChat org account. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher has strong track record across 38 approved CometChat packages. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org-wide maintainer rotation, not takeover. | ai | |
| provenance | no-provenance | AI (provenance): Established CometChat package; lack of provenance is consistent across all prior versions and is not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@types/prop-types | AI (phantom-deps): Type-only package loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types is a declared runtime dep used by convention in React Native packages; stable false positive. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 5.3.10 | 7 / 13 | |
| 5.3.9 | 7 / 13 | |
| 5.3.8 | 7 / 13 | |
| 5.3.7 | 7 / 13 | |
| 5.3.6 | 7 / 13 | |
| 5.3.5 | 6 / 13 | |
| 5.3.4 | 6 / 13 | |
| 5.3.3 | 6 / 13 | |
| 5.3.2 | 6 / 13 | |
| 5.3.1 | 6 / 13 | |
| 5.3.0 | 6 / 13 | |
| 5.2.11 | 6 / 13 | |
| 5.2.10 | 6 / 13 | |
| 5.2.9 | 6 / 13 | |
| 5.2.8 | 6 / 13 | |
| 5.2.7 | 6 / 13 | |
| 5.2.6 | 6 / 13 | |
| 5.2.5 | 6 / 13 | |
| 5.2.4 | 6 / 13 | |
| 5.2.3 | 6 / 13 | |
| 5.2.2 | 6 / 13 | |
| 5.2.1 | 6 / 13 | |
| 5.0.2 | 2 / 13 | |
| 5.0.0 | 0 / 13 | |
| 4.3.27 | 3 / 17 |
v5.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-27. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.10
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (honey-cometchat) than the most recent previously approved version (suraj-cometchat) on 2026-02-05, 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.
v5.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-01-20. This could indicate a legitimate maintainer transition or an account compromise.
v5.2.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (williamshepherd) than the most recent previously approved version (honey-cometchat) on 2025-12-17, but williamshepherd 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.
v5.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (williamshepherd) than the most recent previously approved version (honey-cometchat) on 2025-11-17, but williamshepherd 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.
v5.2.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (williamshepherd) than the most recent previously approved version (honey-cometchat) on 2025-11-14, but williamshepherd 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.
v5.2.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (williamshepherd) than the most recent previously approved version (honey-cometchat) on 2025-10-29, but williamshepherd 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.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.27
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: honey-cometchat.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.