@conclave-ai/core
Conclave AI core — Agent interface, council orchestration, self-evolve substrate, efficiency gate.
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 AI package; name similarity to 'cors' is coincidental, not impersonation. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 0.14.2 | 1 / 1 | |
| 0.14.1 | 1 / 1 | |
| 0.14.0 | 1 / 1 | |
| 0.13.1 | 1 / 1 | |
| 0.13.0 | 1 / 1 | |
| 0.12.23 | 1 / 1 | |
| 0.12.22 | 1 / 1 | |
| 0.12.21 | 1 / 1 | |
| 0.12.20 | 1 / 1 | |
| 0.12.19 | 1 / 1 | |
| 0.12.18 | 1 / 1 | |
| 0.12.17 | 1 / 1 | |
| 0.12.16 | 1 / 1 | |
| 0.12.15 | 1 / 1 | |
| 0.12.14 | 1 / 1 | |
| 0.12.13 | 1 / 1 | |
| 0.12.12 | 1 / 1 | |
| 0.12.11 | 1 / 1 | |
| 0.12.10 | 1 / 1 | |
| 0.12.9 | 1 / 1 | |
| 0.12.8 | 1 / 1 | |
| 0.12.7 | 1 / 1 | |
| 0.12.6 | 1 / 1 | |
| 0.12.5 | 1 / 1 | |
| 0.12.4 | 1 / 1 | |
| 0.12.3 | 1 / 1 | |
| 0.12.2 | 1 / 1 | |
| 0.12.1 | 1 / 1 | |
| 0.12.0 | 1 / 1 | |
| 0.11.23 | 1 / 1 | |
| 0.11.21 | 1 / 1 | |
| 0.11.20 | 1 / 1 | |
| 0.11.19 | 1 / 1 | |
| 0.11.18 | 1 / 1 | |
| 0.11.17 | 1 / 1 | |
| 0.11.16 | 1 / 1 | |
| 0.11.15 | 1 / 1 | |
| 0.11.14 | 1 / 1 | |
| 0.11.13 | 1 / 1 | |
| 0.11.12 | 1 / 1 | |
| 0.11.11 | 1 / 1 | |
| 0.11.10 | 1 / 1 | |
| 0.11.9 | 1 / 1 | |
| 0.11.8 | 1 / 1 | |
| 0.11.7 | 1 / 1 | |
| 0.11.6 | 1 / 1 | |
| 0.11.5 | 1 / 1 | |
| 0.11.4 | 1 / 1 | |
| 0.11.3 | 1 / 1 | |
| 0.11.2 | 1 / 1 | |
| 0.11.1 | 1 / 1 |
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
2 findingsPackage name '@conclave-ai/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.14.0
2 findingsPackage name '@conclave-ai/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.13.1
2 findingsPackage name '@conclave-ai/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.13.0
2 findingsPackage name '@conclave-ai/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.12.23
2 findingsPackage name '@conclave-ai/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.12.22
2 findingsPackage name '@conclave-ai/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.12.21
2 findingsPackage name '@conclave-ai/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.12.20
2 findingsPackage name '@conclave-ai/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.12.18
2 findingsPackage name '@conclave-ai/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.12.17
2 findingsPackage name '@conclave-ai/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.12.16
2 findingsPackage name '@conclave-ai/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.12.15
2 findingsPackage name '@conclave-ai/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.12.14
2 findingsPackage name '@conclave-ai/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.12.13
2 findingsPackage name '@conclave-ai/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.12.12
2 findingsPackage name '@conclave-ai/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.12.11
2 findingsPackage name '@conclave-ai/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.12.10
2 findingsPackage name '@conclave-ai/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.12.9
2 findingsPackage name '@conclave-ai/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.12.8
2 findingsPackage name '@conclave-ai/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.12.7
2 findingsPackage name '@conclave-ai/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.12.6
2 findingsPackage name '@conclave-ai/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.12.5
2 findingsPackage name '@conclave-ai/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.12.3
2 findingsPackage name '@conclave-ai/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.12.2
2 findingsPackage name '@conclave-ai/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.12.0
2 findingsPackage name '@conclave-ai/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.11.23
2 findingsPackage name '@conclave-ai/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.11.21
2 findingsPackage name '@conclave-ai/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.11.19
2 findingsPackage name '@conclave-ai/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.11.18
2 findingsPackage name '@conclave-ai/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.11.17
2 findingsPackage name '@conclave-ai/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.11.16
2 findingsPackage name '@conclave-ai/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.11.15
2 findingsPackage name '@conclave-ai/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.11.14
2 findingsPackage name '@conclave-ai/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.11.13
2 findingsPackage name '@conclave-ai/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.11.12
2 findingsPackage name '@conclave-ai/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.11.10
2 findingsPackage name '@conclave-ai/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.11.9
2 findingsPackage name '@conclave-ai/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.11.8
2 findingsPackage name '@conclave-ai/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.11.7
2 findingsPackage name '@conclave-ai/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.11.6
2 findingsPackage name '@conclave-ai/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.11.5
2 findingsPackage name '@conclave-ai/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.11.3
2 findingsPackage name '@conclave-ai/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.11.2
2 findingsPackage name '@conclave-ai/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.11.1
2 findingsPackage name '@conclave-ai/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.