@blueking/chat-x
蓝鲸智云 AI Chat 组件库 —— 遵循 AG-UI，为 AI Agent 和人类开发者共同设计的对话 UI 组件库。
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is declared and used in config/build; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Encoded string is the entities library HTML decode data table (base64 lookup), a known benign pattern in bundled UI libs. | ai | |
| dependencies | unvetted-dep:bkui-vue | AI (dependencies): bkui-vue is the official BlueKing UI library, consistent with this package's ecosystem. | ai | |
| dependencies | unvetted-dep:vue-tippy | AI (dependencies): vue-tippy is a well-known Vue wrapper for tippy.js; no malware indicators. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.0.36 | 17 / 29 | |
| 0.0.34 | 17 / 29 | |
| 0.0.33 | 17 / 29 | |
| 0.0.29 | 17 / 29 | |
| 0.0.26 | 17 / 29 | |
| 0.0.25 | 17 / 29 | |
| 0.0.24 | 17 / 29 | |
| 0.0.23 | 17 / 29 | |
| 0.0.22 | 17 / 28 | |
| 0.0.21 | 17 / 28 | |
| 0.0.20 | 17 / 28 | |
| 0.0.19 | 15 / 29 | |
| 0.0.18 | 15 / 29 | |
| 0.0.16 | 15 / 29 | |
| 0.0.15 | 13 / 31 | |
| 0.0.14 | 13 / 31 | |
| 0.0.12 | 13 / 31 | |
| 0.0.11 | 13 / 31 | |
| 0.0.10 | 13 / 31 | |
| 0.0.9 | 13 / 31 | |
| 0.0.8 | 14 / 31 | |
| 0.0.2 | 13 / 27 |
v0.0.36
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.29
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.