← Home

@cognigy/chat-components

[![ESLint](https://github.com/Cognigy/chat-components/actions/workflows/eslint.yml/badge.svg)](https://github.com/Cognigy/chat-components/actions/workflows/eslint.yml)

20
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

mayrbenjamin92pedilykwintodshirelkolappcatharsis68cu4nt0mx.jordarchhetri-cognigyfkhalidlucasdssramosf.asadjortegadiazcognigymastasky

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:new-function-constructor AI (semgrep): Intentional pattern: evaluates user-configured flatpickr enable/disable function string for date picker; stable across versions. ai
dependencies unvetted-dep:@fontsource/figtree AI (dependencies): @fontsource/figtree is a standard Google Fonts package; no security concerns. ai

Versions (showing 20 of 20)

Version Deps Published
0.78.0 16 / 31
0.77.0 16 / 31
0.76.0 16 / 28
0.75.1 16 / 28
0.75.0 16 / 28
0.74.0 15 / 28
0.73.0 15 / 28
0.72.0 15 / 28
0.71.0 15 / 28
0.70.0 15 / 27
0.69.0 15 / 27
0.68.0 15 / 27
0.67.0 15 / 27
0.66.0 15 / 27
0.65.1 15 / 27
0.65.0 15 / 27
0.64.0 15 / 26
0.63.0 16 / 26
0.62.0 16 / 26
0.22.0 10 / 28

v0.78.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.77.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.69.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.68.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.67.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: lkolapp → GitHub Actions (on 2026-02-09, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (lkolapp) on 2026-02-09, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v0.66.0

1 finding
LOW No provenance attestation provenance

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

v0.65.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: kwinto → lkolapp (on 2025-12-19, known maintainer) provenance

This version was published by a different npm account (lkolapp) than the most recent previously approved version (kwinto) on 2025-12-19, but lkolapp is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.65.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: kwinto → lkolapp (on 2025-12-15, known maintainer) provenance

This version was published by a different npm account (lkolapp) than the most recent previously approved version (kwinto) on 2025-12-15, but lkolapp is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.64.0

1 finding
LOW No provenance attestation provenance

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

v0.63.0

1 finding
LOW No provenance attestation provenance

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

v0.62.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.

v0.22.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.