← Home

@bdky/aaas-pilot-kit-react-widget

npm

百度数字员工 AaaS Pilot Kit 的 React UI 组件库，开箱即用的数字员工 UI 组件，5 分钟搭建完整交互界面

14
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

zhangwx616berwin0415patrickli147

Keywords

reactreact-componentsui-componentschat-uidigital-employeedigital-human数字员工数字人ai-assistantchatbotbaidu百度客悦

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:classnames AI (phantom-deps): classnames is a declared runtime dependency; phantom-dep heuristic fires incorrectly for this bundled component library. ai
phantom-deps phantom-dep:use-stick-to-bottom AI (phantom-deps): use-stick-to-bottom is a declared runtime dependency; phantom-dep heuristic fires incorrectly for this bundled component library. ai

Versions (showing 14 of 14)

Version Deps Published
1.0.13 4 / 6
1.0.12 4 / 6
1.0.11 4 / 6
1.0.10 4 / 6
1.0.9 4 / 6
1.0.8 4 / 6
1.0.7 4 / 6
1.0.6 4 / 6
1.0.5 4 / 6
1.0.4 4 / 6
1.0.3 4 / 6
1.0.2 4 / 6
1.0.1 4 / 6
1.0.0 4 / 6

v1.0.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.