@tencentcloud/chat
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:modules/cloud-search-module.js | AI (source-diff): Minified bundled module using official Tencent Cloud endpoints, not obfuscation with malicious behavior. | ai | |
| phantom-deps | phantom-dep:@tencentcloud/uni-app-push | AI (phantom-deps): Same-org companion package, optional platform integration, not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@tencentcloud/react-native-push | AI (phantom-deps): Same-org optional RN push integration, not directly imported by design. | ai | |
| dependencies | unvetted-dep:@tencentcloud/react-native-push | AI (dependencies): First-party Tencent Cloud sibling package, consistent with publisher's trusted track record. | ai | |
| typosquat | typosquat.levenshtein:chalk | AI (typosquat): Scoped Tencent Cloud SDK; name similarity to chalk is coincidental, not a typosquat. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 3.6.6 | 0 / 0 | |
| 3.6.5 | 0 / 0 | |
| 3.6.4 | 0 / 0 | |
| 3.6.3 | 0 / 0 | |
| 3.6.2 | 0 / 0 | |
| 3.6.1 | 0 / 0 | |
| 3.6.0 | 0 / 0 | |
| 3.5.9 | 0 / 0 | |
| 3.5.8 | 0 / 0 | |
| 3.5.7 | 0 / 0 | |
| 3.5.6 | 0 / 0 | |
| 3.5.5 | 0 / 0 | |
| 3.5.4 | 0 / 0 | |
| 3.5.3 | 0 / 0 | |
| 3.5.2 | 2 / 0 | |
| 3.5.1 | 2 / 0 | |
| 3.5.0 | 2 / 0 | |
| 3.4.9 | 2 / 0 | |
| 3.4.8 | 2 / 0 | |
| 3.4.7 | 2 / 0 | |
| 3.4.6 | 2 / 0 | |
| 3.4.5 | 2 / 0 | |
| 3.4.4 | 1 / 0 | |
| 3.4.3 | 0 / 0 | |
| 3.4.2 | 0 / 0 | |
| 3.4.1 | 0 / 0 | |
| 3.4.0 | 0 / 0 | |
| 3.3.5 | 0 / 0 |
v3.5.4
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (allen0809npm) than the most recent previously approved version (yangq) on 2025-04-10, but allen0809npm 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.
v3.5.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (allen0809npm) than the most recent previously approved version (yangq) on 2025-03-25, but allen0809npm 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.
v3.5.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.