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, 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 |
|---|---|---|---|---|
| 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 100 of 438)
| Version | Deps | Published |
|---|---|---|
| 4.1.250 | 2 / 19 | |
| 4.1.249 | 2 / 19 | |
| 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 | |
| 4.1.27 | 2 / 18 | |
| 4.1.24 | 2 / 18 | |
| 4.1.23 | 2 / 18 | |
| 4.1.20 | 2 / 18 | |
| 4.1.19 | 2 / 18 | |
| 4.1.11 | 2 / 18 | |
| 4.1.10 | 2 / 18 | |
| 4.1.8 | 2 / 18 | |
| 4.1.7 | 2 / 18 | |
| 4.0.1029 | 2 / 10 | |
| 4.0.1028 | 2 / 10 | |
| 4.0.1013 | 2 / 10 | |
| 4.0.1012 | 2 / 10 | |
| 4.0.980 | 2 / 10 | |
| 4.0.979 | 2 / 10 | |
| 4.0.964 | 2 / 10 | |
| 4.0.963 | 2 / 10 | |
| 4.0.956 | 2 / 10 | |
| 4.0.955 | 2 / 10 | |
| 4.0.948 | 2 / 10 | |
| 4.0.947 | 2 / 10 | |
| 4.0.906 | 2 / 10 | |
| 4.0.905 | 2 / 10 | |
| 4.0.894 | 2 / 10 | |
| 4.0.893 | 2 / 10 | |
| 4.0.859 | 1 / 10 | |
| 4.0.858 | 1 / 10 | |
| 4.0.849 | 1 / 10 | |
| 4.0.848 | 1 / 10 | |
| 4.0.841 | 1 / 10 | |
| 4.0.818 | 1 / 10 | |
| 4.0.817 | 1 / 10 | |
| 4.0.814 | 1 / 10 | |
| 4.0.813 | 1 / 10 | |
| 4.0.810 | 1 / 10 | |
| 4.0.809 | 1 / 10 | |
| 4.0.795 | 1 / 10 | |
| 4.0.794 | 1 / 10 | |
| 4.0.793 | 1 / 10 | |
| 4.0.784 | 1 / 10 | |
| 4.0.783 | 1 / 10 | |
| 4.0.781 | 1 / 10 | |
| 4.0.780 | 1 / 10 | |
| 4.0.779 | 1 / 10 | |
| 4.0.778 | 1 / 10 | |
| 4.0.777 | 1 / 10 | |
| 4.0.776 | 1 / 10 | |
| 4.0.775 | 1 / 10 | |
| 4.0.774 | 1 / 10 | |
| 4.0.773 | 1 / 10 |
v4.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1029
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1028
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1013
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1012
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.980
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.979
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.964
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.963
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.956
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.955
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.948
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.947
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.906
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.905
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.894
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.893
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.859
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.858
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.849
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.848
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.841
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.818
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.817
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.814
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.813
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.810
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.809
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.795
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.794
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.793
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.784
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.783
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.781
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.780
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.779
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.778
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.777
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.776
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.775
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.774
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.773
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.