@xpert-ai/chatkit-react
React bindings for Xpert Chatkit
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@xpert-ai/chatkit-types | AI (phantom-deps): Same-org type-only dependency; likely used only in type declarations, not direct imports. | ai | |
| phantom-deps | phantom-dep:@xpert-ai/chatkit-web-component | AI (phantom-deps): Same-org monorepo sibling; may be re-exported rather than directly imported. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.1.2 | 2 / 5 | |
| 0.1.1 | 2 / 5 | |
| 0.1.0 | 2 / 5 | |
| 0.0.3 | 2 / 5 | |
| 0.0.2 | 2 / 5 | |
| 0.0.1 | 2 / 5 |
v0.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.3
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: tiven.wang.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.