@copilotkitnext/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped CopilotKit package; name similarity to 'cors' is coincidental, not impersonation. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.54.1 | 5 / 12 | |
| 1.54.0 | 5 / 12 | |
| 1.53.0 | 6 / 8 | |
| 1.52.1 | 5 / 8 | |
| 1.52.0 | 5 / 8 | |
| 1.51.4 | 5 / 8 | |
| 1.51.3 | 5 / 8 | |
| 1.51.2 | 5 / 8 | |
| 1.51.1 | 3 / 9 | |
| 1.51.0 | 3 / 9 | |
| 0.0.33 | 5 / 8 | |
| 0.0.32 | 5 / 8 | |
| 0.0.31 | 5 / 8 | |
| 0.0.30 | 5 / 8 | |
| 0.0.29 | 5 / 8 | |
| 0.0.28 | 5 / 8 | |
| 0.0.27 | 5 / 8 | |
| 0.0.26 | 5 / 8 | |
| 0.0.25 | 5 / 8 | |
| 0.0.24 | 5 / 8 | |
| 0.0.23 | 5 / 8 | |
| 0.0.22 | 5 / 8 |
v1.54.1
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.0
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.0
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.1
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.0
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.4
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.3
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.2
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.1
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.0
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
2 findingsPackage name '@copilotkitnext/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.