@copilotkit/react-ui
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/index.umd.js | AI (source-diff): UMD bundle build output for React UI lib; net+exec pattern is bundler boilerplate, stable FP. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from manual publish to GitHub Actions CI/CD with SLSA provenance; legitimate for this org. | ai | |
| provenance | no-provenance | AI (provenance): CopilotKit consistently publishes without provenance; stable pattern across 65 approved packages. | ai |
Versions (showing 100 of 137)
| Version | Deps | Published |
|---|---|---|
| 1.63.2 | 10 / 12 | |
| 1.63.1 | 10 / 12 | |
| 1.63.0 | 10 / 12 | |
| 1.62.3 | 10 / 12 | |
| 1.62.2 | 10 / 12 | |
| 1.62.1 | 10 / 12 | |
| 1.62.0 | 10 / 12 | |
| 1.61.2 | 10 / 12 | |
| 1.61.1 | 10 / 12 | |
| 1.61.0 | 9 / 11 | |
| 1.60.2 | 9 / 11 | |
| 1.60.1 | 9 / 11 | |
| 1.60.0 | 9 / 11 | |
| 1.59.5 | 9 / 11 | |
| 1.59.4 | 9 / 11 | |
| 1.59.3 | 9 / 11 | |
| 1.59.2 | 9 / 11 | |
| 1.59.1 | 9 / 11 | |
| 1.59.0 | 9 / 11 | |
| 1.58.0 | 9 / 11 | |
| 1.57.4 | 9 / 11 | |
| 1.57.3 | 9 / 11 | |
| 1.57.2 | 9 / 11 | |
| 1.57.1 | 9 / 11 | |
| 1.57.0 | 9 / 11 | |
| 1.56.5 | 9 / 11 | |
| 1.56.4 | 9 / 11 | |
| 1.56.3 | 9 / 11 | |
| 1.56.2 | 9 / 11 | |
| 1.56.1 | 9 / 11 | |
| 1.56.0 | 9 / 11 | |
| 1.55.3 | 9 / 11 | |
| 1.55.2 | 9 / 11 | |
| 1.55.1 | 9 / 11 | |
| 1.55.0 | 9 / 11 | |
| 1.54.1 | 9 / 12 | |
| 1.54.0 | 9 / 12 | |
| 1.53.0 | 9 / 12 | |
| 1.52.1 | 9 / 12 | |
| 1.52.0 | 9 / 12 | |
| 1.51.4 | 9 / 14 | |
| 1.51.3 | 9 / 14 | |
| 1.51.2 | 9 / 14 | |
| 1.51.1 | 6 / 17 | |
| 1.51.0 | 6 / 17 | |
| 1.50.1 | 9 / 14 | |
| 1.50.0 | 9 / 14 | |
| 1.10.6 | 9 / 14 | |
| 1.10.5 | 9 / 14 | |
| 1.10.4 | 9 / 14 | |
| 1.10.3 | 9 / 14 | |
| 1.10.2 | 9 / 14 | |
| 1.10.1 | 9 / 14 | |
| 1.10.0 | 9 / 14 | |
| 1.9.3 | 9 / 14 | |
| 1.9.2 | 9 / 14 | |
| 1.9.1 | 9 / 14 | |
| 1.9.0 | 9 / 14 | |
| 1.8.14 | 9 / 14 | |
| 1.8.13 | 9 / 14 | |
| 1.8.12 | 8 / 14 | |
| 1.8.11 | 8 / 14 | |
| 1.8.10 | 8 / 14 | |
| 1.8.9 | 8 / 14 | |
| 1.8.8 | 8 / 14 | |
| 1.8.7 | 8 / 14 | |
| 1.8.6 | 8 / 14 | |
| 1.8.5 | 8 / 14 | |
| 1.8.4 | 8 / 14 | |
| 1.8.3 | 8 / 14 | |
| 1.8.2 | 8 / 14 | |
| 1.8.1 | 8 / 14 | |
| 1.8.0 | 8 / 14 | |
| 1.7.1 | 8 / 14 | |
| 1.7.0 | 8 / 14 | |
| 1.6.0 | 8 / 14 | |
| 1.5.20 | 8 / 14 | |
| 1.5.19 | 8 / 14 | |
| 1.5.18 | 8 / 14 | |
| 1.5.17 | 8 / 14 | |
| 1.5.16 | 8 / 14 | |
| 1.5.15 | 8 / 14 | |
| 1.5.14 | 8 / 14 | |
| 1.5.13 | 8 / 14 | |
| 1.5.12 | 8 / 14 | |
| 1.5.11 | 8 / 14 | |
| 1.5.10 | 8 / 14 | |
| 1.5.9 | 8 / 14 | |
| 1.5.8 | 8 / 14 | |
| 1.5.7 | 8 / 14 | |
| 1.5.6 | 8 / 14 | |
| 1.5.5 | 8 / 14 | |
| 1.5.4 | 8 / 14 | |
| 1.5.3 | 8 / 14 | |
| 1.5.2 | 8 / 14 | |
| 1.5.1 | 8 / 14 | |
| 1.5.0 | 8 / 14 | |
| 1.4.8 | 8 / 14 | |
| 1.4.7 | 8 / 14 | |
| 1.4.6 | 8 / 14 |
v1.63.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.63.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.63.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.62.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.62.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.62.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.62.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.61.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.51.4
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.3
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.