@cometchat/chat-uikit-vue
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher has strong track record (55 approved, 0 rejected); stale change, no takeover indicators. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with legitimate maintainer transition, not takeover. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Stale change 696d without unpublish; inconsistent with compromise. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): Known implicit runtime dependency. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-alias | AI (phantom-deps): Framework-scoped build convention dep. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 4.3.32 | 4 / 16 | |
| 4.3.31 | 4 / 16 | |
| 4.3.30 | 4 / 16 | |
| 4.3.28 | 4 / 16 | |
| 4.3.27 | 4 / 16 | |
| 4.3.26 | 4 / 16 | |
| 4.3.25 | 4 / 16 | |
| 4.3.24 | 4 / 16 | |
| 4.3.23 | 4 / 16 | |
| 4.3.22 | 4 / 16 | |
| 4.3.21 | 4 / 16 | |
| 4.3.20 | 4 / 16 | |
| 4.3.19 | 4 / 16 | |
| 4.3.18 | 4 / 16 | |
| 4.3.17 | 4 / 16 | |
| 4.3.16 | 4 / 16 | |
| 4.3.15 | 4 / 16 | |
| 4.3.14 | 4 / 16 | |
| 4.3.13 | 4 / 16 | |
| 4.3.12 | 4 / 16 | |
| 4.3.11 | 4 / 16 | |
| 4.3.10 | 4 / 16 | |
| 4.3.9 | 4 / 16 | |
| 4.3.8 | 4 / 16 |
v4.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.22
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rajdubey) than the most recent previously approved version (swayamdebata) on 2025-02-28, 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.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.17
2 findingsThis version was published by a different npm account (swayamdebata) than the most recent previously approved version (birendraprasad.gupta) on 2024-09-24. It has since remained available on npm for 662 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.16
2 findingsThis version was published by a different npm account (swayamdebata) than the most recent previously approved version (nakuljjwcc) on 2024-08-21. It has since remained available on npm for 696 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (birendraprasad.gupta) than the most recent previously approved version (nakuljjwcc) on 2024-08-08, but birendraprasad.gupta 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.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.