@copilotkit/a2ui-renderer
A2UI Renderer for CopilotKit - render A2UI surfaces in React applications
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from copilotkit user to GitHub Actions CI/CD publishing, backed by SLSA provenance attestation. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dep; usage in dist/config files is expected for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Intra-monorepo dep added at matching version; consistent with CopilotKit release pattern. | ai | |
| dependencies | unvetted-dep:@lit-labs/signals | AI (dependencies): @lit-labs/signals is a Google/Lit-team library; legitimate use in a Lit-based renderer, not a risk. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a widely-used, well-maintained Markdown parser with no malicious history. | ai | |
| provenance | no-provenance | AI (provenance): CopilotKit org consistently publishes without Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 1.59.5 | 4 / 9 | |
| 1.59.4 | 4 / 9 | |
| 1.59.3 | 4 / 9 | |
| 1.59.2 | 4 / 9 | |
| 1.59.1 | 4 / 9 | |
| 1.59.0 | 4 / 9 | |
| 1.58.0 | 4 / 9 | |
| 1.57.4 | 4 / 9 | |
| 1.57.3 | 4 / 8 | |
| 1.57.2 | 4 / 8 | |
| 1.57.1 | 4 / 8 | |
| 1.57.0 | 4 / 8 | |
| 1.56.5 | 4 / 8 | |
| 1.56.4 | 4 / 8 | |
| 1.56.3 | 4 / 8 | |
| 1.56.2 | 4 / 8 | |
| 1.56.1 | 4 / 8 | |
| 1.56.0 | 4 / 8 | |
| 1.55.3 | 4 / 8 | |
| 1.55.2 | 4 / 8 | |
| 1.55.1 | 4 / 8 | |
| 1.55.0 | 4 / 8 | |
| 1.54.1 | 4 / 8 | |
| 1.54.0 | 4 / 8 | |
| 1.53.0 | 4 / 8 | |
| 1.52.1 | 4 / 8 | |
| 1.52.0 | 4 / 8 | |
| 1.51.4 | 4 / 7 | |
| 1.51.3 | 6 / 6 | |
| 1.51.2 | 6 / 3 | |
| 1.51.1 | 5 / 4 | |
| 1.51.0 | 5 / 4 | |
| 1.50.1 | 5 / 4 | |
| 0.0.2 | 5 / 4 | |
| 0.0.1 | 5 / 4 |
v1.59.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.59.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.59.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.59.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.59.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.59.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.58.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.57.4
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.57.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.54.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.1
1 finding[Accepted risk] 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.