@botonic/webchat-core
Framework-agnostic primitives for Botonic webchat behavior and state, used by `@botonic/webchat-react` and bot apps on the **current** line.
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
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): Monorepo sub-package of @botonic suite; inflated semver and sparse metadata are structural, not spam indicators. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.27.0 | 5 / 0 | |
| 2.26.0 | 5 / 0 | |
| 2.25.0 | 5 / 0 | |
| 2.24.0 | 5 / 0 | |
| 2.23.2 | 5 / 0 | |
| 2.23.1 | 5 / 0 | |
| 2.23.0 | 5 / 0 |
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.