tencentcloud-sdk-nodejs-cdn
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Tencent Cloud SDK suite; mass-production and link-dump signals are expected for a large vendor SDK family. | ai | |
| dependencies | unvetted-dep:tencentcloud-sdk-nodejs-common | AI (dependencies): Same-vendor shared library; stable dependency pattern across all versions of this SDK suite. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 4.1.200 | 2 / 19 | |
| 4.1.199 | 2 / 19 | |
| 4.1.194 | 2 / 19 | |
| 4.1.193 | 2 / 19 | |
| 4.1.161 | 2 / 19 | |
| 4.1.160 | 2 / 19 | |
| 4.1.159 | 2 / 19 | |
| 4.1.158 | 2 / 19 | |
| 4.1.157 | 2 / 19 | |
| 4.1.147 | 2 / 19 | |
| 4.1.146 | 2 / 19 | |
| 4.1.138 | 2 / 19 | |
| 4.1.137 | 2 / 19 | |
| 4.1.131 | 2 / 19 | |
| 4.1.130 | 2 / 19 | |
| 4.1.122 | 2 / 19 | |
| 4.1.120 | 2 / 18 | |
| 4.1.119 | 2 / 18 | |
| 4.1.116 | 2 / 18 | |
| 4.1.115 | 2 / 18 | |
| 4.1.94 | 2 / 18 | |
| 4.1.93 | 2 / 18 | |
| 4.1.92 | 2 / 18 | |
| 4.1.91 | 2 / 18 | |
| 4.1.86 | 2 / 18 | |
| 4.1.85 | 2 / 18 | |
| 4.1.80 | 2 / 18 | |
| 4.1.79 | 2 / 18 | |
| 4.1.78 | 2 / 18 | |
| 4.1.77 | 2 / 18 | |
| 4.1.76 | 2 / 18 | |
| 4.1.75 | 2 / 18 | |
| 4.1.74 | 2 / 18 | |
| 4.1.73 | 2 / 18 | |
| 4.1.71 | 2 / 18 | |
| 4.1.70 | 2 / 18 | |
| 4.1.64 | 2 / 18 | |
| 4.1.63 | 2 / 18 | |
| 4.1.58 | 2 / 18 | |
| 4.1.57 | 2 / 18 | |
| 4.1.56 | 2 / 18 | |
| 4.1.55 | 2 / 18 | |
| 4.1.49 | 2 / 18 | |
| 4.1.48 | 2 / 18 | |
| 4.1.32 | 2 / 18 | |
| 4.1.31 | 2 / 18 | |
| 4.1.29 | 2 / 18 | |
| 4.1.28 | 2 / 18 |
v4.1.199
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.194
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.193
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.161
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.159
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.158
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.157
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.147
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.146
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.137
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.