@bdky/aaas-pilot-kit-vue3-widget
百度数字员工 AaaS Pilot Kit 的 Vue 3 UI 组件库，开箱即用的数字员工 UI 组件，5 分钟搭建完整交互界面
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): @vueuse/core is a declared runtime dependency; phantom-dep fires because it's not directly imported in analyzed entry points, not a real concern. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present to elevate this. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.0.13 | 2 / 6 | |
| 1.0.12 | 2 / 6 | |
| 1.0.11 | 2 / 6 | |
| 1.0.10 | 2 / 6 | |
| 1.0.9 | 2 / 6 | |
| 1.0.8 | 2 / 6 | |
| 1.0.7 | 2 / 6 | |
| 1.0.6 | 2 / 6 | |
| 1.0.5 | 2 / 6 | |
| 1.0.4 | 2 / 6 | |
| 1.0.3 | 2 / 6 | |
| 1.0.2 | 2 / 6 | |
| 1.0.1 | 2 / 6 | |
| 1.0.0 | 2 / 6 |
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.