@dcloudio/uni-app-x
uni-app x types
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
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): Types-only distribution package from established DCloud org; sparse metadata is expected for this package type. | ai |
Versions (showing 99 of 99)
| Version | Deps | Published |
|---|---|---|
| 0.7.123 | 0 / 9 | |
| 0.7.122 | 0 / 9 | |
| 0.7.121 | 0 / 9 | |
| 0.7.113 | 0 / 9 | |
| 0.7.112 | 0 / 9 | |
| 0.7.111 | 0 / 9 | |
| 0.7.109 | 0 / 9 | |
| 0.7.108 | 0 / 9 | |
| 0.7.107 | 0 / 9 | |
| 0.7.106 | 0 / 9 | |
| 0.7.105 | 0 / 9 | |
| 0.7.104 | 0 / 9 | |
| 0.7.103 | 0 / 9 | |
| 0.7.102 | 0 / 9 | |
| 0.7.101 | 0 / 9 | |
| 0.7.100 | 0 / 9 | |
| 0.7.99 | 0 / 9 | |
| 0.7.98 | 0 / 9 | |
| 0.7.97 | 0 / 9 | |
| 0.7.96 | 0 / 9 | |
| 0.7.95 | 0 / 9 | |
| 0.7.94 | 0 / 9 | |
| 0.7.93 | 0 / 9 | |
| 0.7.92 | 0 / 9 | |
| 0.7.90 | 0 / 9 | |
| 0.7.89 | 0 / 9 | |
| 0.7.88 | 0 / 9 | |
| 0.7.87 | 0 / 9 | |
| 0.7.86 | 0 / 9 | |
| 0.7.85 | 0 / 9 | |
| 0.7.84 | 0 / 9 | |
| 0.7.82 | 0 / 9 | |
| 0.7.81 | 0 / 9 | |
| 0.7.80 | 0 / 9 | |
| 0.7.78 | 0 / 8 | |
| 0.7.77 | 0 / 8 | |
| 0.7.76 | 0 / 8 | |
| 0.7.75 | 0 / 8 | |
| 0.7.74 | 0 / 8 | |
| 0.7.73 | 0 / 8 | |
| 0.7.72 | 0 / 8 | |
| 0.7.71 | 0 / 8 | |
| 0.7.70 | 0 / 8 | |
| 0.7.69 | 0 / 8 | |
| 0.7.68 | 0 / 8 | |
| 0.7.67 | 0 / 8 | |
| 0.7.66 | 0 / 8 | |
| 0.7.65 | 0 / 7 | |
| 0.7.64 | 0 / 7 | |
| 0.7.63 | 0 / 7 | |
| 0.7.62 | 0 / 7 | |
| 0.7.61 | 0 / 7 | |
| 0.7.60 | 0 / 7 | |
| 0.7.59 | 0 / 7 | |
| 0.7.58 | 0 / 7 | |
| 0.7.57 | 0 / 7 | |
| 0.7.56 | 0 / 7 | |
| 0.7.55 | 0 / 7 | |
| 0.7.54 | 0 / 7 | |
| 0.7.53 | 0 / 7 | |
| 0.7.52 | 0 / 7 | |
| 0.7.51 | 0 / 7 | |
| 0.7.50 | 0 / 7 | |
| 0.7.49 | 0 / 7 | |
| 0.7.48 | 0 / 7 | |
| 0.7.47 | 0 / 7 | |
| 0.7.46 | 0 / 7 | |
| 0.7.45 | 0 / 7 | |
| 0.7.44 | 0 / 7 | |
| 0.7.43 | 0 / 7 | |
| 0.7.42 | 0 / 7 | |
| 0.7.41 | 0 / 7 | |
| 0.7.40 | 0 / 7 | |
| 0.7.39 | 0 / 6 | |
| 0.7.38 | 0 / 6 | |
| 0.7.37 | 0 / 6 | |
| 0.7.36 | 0 / 6 | |
| 0.7.35 | 0 / 6 | |
| 0.7.34 | 0 / 6 | |
| 0.7.33 | 0 / 6 | |
| 0.7.32 | 0 / 6 | |
| 0.7.31 | 0 / 6 | |
| 0.7.30 | 0 / 6 | |
| 0.7.29 | 0 / 6 | |
| 0.7.28 | 0 / 6 | |
| 0.7.27 | 0 / 6 | |
| 0.7.26 | 0 / 6 | |
| 0.7.25 | 0 / 6 | |
| 0.7.24 | 0 / 6 | |
| 0.7.23 | 0 / 6 | |
| 0.7.22 | 0 / 6 | |
| 0.7.21 | 0 / 6 | |
| 0.7.20 | 0 / 6 | |
| 0.7.19 | 0 / 6 | |
| 0.7.18 | 0 / 6 | |
| 0.7.17 | 0 / 6 | |
| 0.7.16 | 0 / 6 | |
| 0.7.15 | 0 / 6 | |
| 0.7.14 | 0 / 6 |
v0.7.113
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 (liuxiaohang) than the most recent previously approved version (fxy060608) on 2026-03-18, but liuxiaohang 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.
v0.7.76
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 (guoshengqiang) than the most recent previously approved version (fxy060608) on 2025-11-11, but guoshengqiang 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.
v0.7.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.