← Home

@copilotkit/channels

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

copilotkit

Keywords

aiagentbotchatbotchannelsslackmicrosoft-teamsteamsintelligencediscordtelegramwhatsappcopilotkitag-ui

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@copilotkit/channels-teams AI (dependencies): Sibling package from same monorepo/org, part of intentional split architecture. ai
publish-pattern new-deps-added AI (publish-pattern): Expected from restructuring into per-channel sub-packages within same org. ai
source-diff large-new-source-files AI (source-diff): Meta-package split explains new file layout, not injected code. ai

Versions (showing 3 of 3)

Version Deps Published
0.2.0 8 / 4
0.1.1 6 / 5
0.1.0 6 / 5

v0.2.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.1.1

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: copilotkit → GitHub Actions (on 2026-07-10, 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 (copilotkit) on 2026-07-10, 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.1.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.