@conarium-ai/core 0.1.0 → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +48 -4
- package/README.md +32 -13
- package/examples/claude-desktop-config.json +1 -1
- package/examples/cursor-mcp-settings.json +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,13 +2,57 @@
|
|
|
2
2
|
|
|
3
3
|
## Unreleased
|
|
4
4
|
|
|
5
|
-
Nothing yet — 0.1.
|
|
5
|
+
Nothing yet — 0.1.1 is the current cut.
|
|
6
|
+
|
|
7
|
+
## 0.1.1 — 2026-08-13
|
|
8
|
+
|
|
9
|
+
Patch. The shipped MCP examples told you to run a command that cannot run.
|
|
10
|
+
|
|
11
|
+
### Fixed
|
|
12
|
+
|
|
13
|
+
- **`examples/cursor-mcp-settings.json` and `examples/claude-desktop-config.json`
|
|
14
|
+
proposed `npx -y @conarium-ai/core`, which fails with `could not determine
|
|
15
|
+
executable to run`.** The package ships eight commands and none of them is
|
|
16
|
+
named `core`, so npx has nothing to pick. Anyone who pasted the example into
|
|
17
|
+
Cursor or Claude Desktop hit a wall on their first attempt — the worst possible
|
|
18
|
+
moment. The working form, measured rather than assumed:
|
|
19
|
+
|
|
20
|
+
```json
|
|
21
|
+
{ "command": "npx",
|
|
22
|
+
"args": ["-y", "--package=@conarium-ai/core", "conarium",
|
|
23
|
+
"--config", "/path/to/your/conarium.config.json"] }
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
- The README MCP client block said `"command": "node", "args": ["dist/index.js"]`
|
|
27
|
+
— the from-source path, wrong for anyone who installed the package.
|
|
28
|
+
|
|
29
|
+
### Changed
|
|
30
|
+
|
|
31
|
+
- README Quick Start leads with the npm install path now that the package is
|
|
32
|
+
published; the from-source route is kept, folded into a `<details>`.
|
|
6
33
|
|
|
7
34
|
## 0.1.0 — 2026-08-13
|
|
8
35
|
|
|
9
|
-
First product cut
|
|
10
|
-
|
|
11
|
-
|
|
36
|
+
First product cut, published to npm as `@conarium-ai/core@0.1.0`.
|
|
37
|
+
|
|
38
|
+
### Fixed before it shipped — `bin` entries were being stripped
|
|
39
|
+
|
|
40
|
+
The first publish attempt failed on 2FA, and the failure was lucky. Its output
|
|
41
|
+
carried this, once per command:
|
|
42
|
+
|
|
43
|
+
```
|
|
44
|
+
npm warn publish "bin[conarium-doctor]" ... was invalid and removed
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
npm was dropping **all eight** command entries, because the values began with
|
|
48
|
+
`./`. Published that way, `npx conarium-doctor` would not have existed — the
|
|
49
|
+
whole point of a one-download install. `npm pack` was never affected, so the
|
|
50
|
+
tarball looked correct the entire time; what npm rewrote was the metadata sent
|
|
51
|
+
to the registry. Fixed with npm's own `npm pkg fix` (`./bin/x.mjs` → `bin/x.mjs`)
|
|
52
|
+
and verified against the published package: eight bins present.
|
|
53
|
+
|
|
54
|
+
**Lesson worth keeping: a correct `npm pack` does not mean a correct
|
|
55
|
+
`npm publish`. Read the `warn` lines in `npm publish --dry-run`.**
|
|
12
56
|
|
|
13
57
|
### Added — install without us in the loop
|
|
14
58
|
|
package/README.md
CHANGED
|
@@ -51,8 +51,10 @@ silinmediğini, yeniden sıralanmadığını ve geriye dönük tarihlenmediğini
|
|
|
51
51
|
kanıtlar. **Oluşturma anında doğru olduğunu kanıtlamaz.**
|
|
52
52
|
|
|
53
53
|
```bash
|
|
54
|
-
# Generate an Ed25519 keypair (private PEM + .pub.pem + .keyid sidecars)
|
|
55
|
-
|
|
54
|
+
# Generate an Ed25519 keypair (private PEM + .pub.pem + .keyid sidecars).
|
|
55
|
+
# The .keyid sidecars are not optional: without them the verifier answers 13
|
|
56
|
+
# for every receipt, which reads like tampering and is not.
|
|
57
|
+
npx conarium-init
|
|
56
58
|
|
|
57
59
|
export CONARIUM_AUDIT_SIGNING_KEY=./audit-ed25519.pem
|
|
58
60
|
|
|
@@ -274,28 +276,42 @@ graph LR
|
|
|
274
276
|
|
|
275
277
|
## 🚀 Quick Start
|
|
276
278
|
|
|
277
|
-
Conarium runs from source today. `@conarium-ai/core` is **not on the npm
|
|
278
|
-
registry yet** — do not expect `npx @conarium-ai/core` to work until it is
|
|
279
|
-
published. The commands below are what works now.
|
|
280
|
-
|
|
281
279
|
```bash
|
|
282
|
-
# 1.
|
|
283
|
-
|
|
284
|
-
cd conarium
|
|
285
|
-
npm install && npm run build
|
|
280
|
+
# 1. Install
|
|
281
|
+
npm i @conarium-ai/core
|
|
286
282
|
|
|
287
283
|
# 2. Write a fail-closed skeleton (config + Ed25519 pair + .keyid sidecars)
|
|
288
|
-
|
|
284
|
+
npx conarium-init
|
|
289
285
|
export CONARIUM_AUDIT_SIGNING_KEY="$PWD/audit-ed25519.pem"
|
|
290
286
|
|
|
291
287
|
# 3. Check the install before trusting it
|
|
292
|
-
|
|
288
|
+
npx conarium-doctor
|
|
293
289
|
|
|
294
290
|
# 4. Point the generated conarium.config.json at your read-only DSN,
|
|
295
291
|
# fill policy.allowTables, then run the governed MCP gateway
|
|
292
|
+
npx conarium
|
|
293
|
+
```
|
|
294
|
+
|
|
295
|
+
Step 3 is not decoration. A missing config file does **not** stop the gateway —
|
|
296
|
+
it starts with zero connectors and governs nothing — and a connector that fails
|
|
297
|
+
to connect is logged, not raised. `conarium-doctor` names both, exits `1` when
|
|
298
|
+
something is wrong so it can gate a deployment, and never prints a secret, so
|
|
299
|
+
its output is safe to paste into an issue.
|
|
300
|
+
|
|
301
|
+
<details>
|
|
302
|
+
<summary>From source instead</summary>
|
|
303
|
+
|
|
304
|
+
```bash
|
|
305
|
+
git clone https://github.com/dogrucanemek-alt/conarium.git
|
|
306
|
+
cd conarium
|
|
307
|
+
npm install && npm run build
|
|
308
|
+
node bin/conarium-init.mjs
|
|
309
|
+
node bin/conarium-doctor.mjs --no-net
|
|
296
310
|
npm start
|
|
297
311
|
```
|
|
298
312
|
|
|
313
|
+
</details>
|
|
314
|
+
|
|
299
315
|
`conarium-init` refuses to overwrite existing files unless you pass `--force`.
|
|
300
316
|
It never prints the private key — only its path.
|
|
301
317
|
|
|
@@ -323,7 +339,10 @@ Conarium speaks MCP over **stdio**, so your AI assistant launches it as a comman
|
|
|
323
339
|
```json
|
|
324
340
|
{
|
|
325
341
|
"mcpServers": {
|
|
326
|
-
"conarium": {
|
|
342
|
+
"conarium": {
|
|
343
|
+
"command": "npx",
|
|
344
|
+
"args": ["-y", "--package=@conarium-ai/core", "conarium", "--config", "/path/to/your/conarium.config.json"]
|
|
345
|
+
}
|
|
327
346
|
}
|
|
328
347
|
}
|
|
329
348
|
```
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"mcpServers": {
|
|
4
4
|
"conarium": {
|
|
5
5
|
"command": "npx",
|
|
6
|
-
"args": ["-y", "
|
|
6
|
+
"args": ["-y", "--package=@conarium-ai/core", "conarium", "--config", "/path/to/your/conarium.config.json"],
|
|
7
7
|
"description": "Conarium — company-aware AI context"
|
|
8
8
|
}
|
|
9
9
|
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@conarium-ai/core",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1",
|
|
4
4
|
"//files": "Pakete NE gireceginin izin listesi. Liste olmadan npm her seyi gonderiyordu: 296 dosya / 1.5 MB — CI workflowlari, gitleaks ayari, 137 KB pazarlama gorseli, sitenin api/chat.js dosyasi. Bir bankanin guvenlik ekibi tarball'i acip bunlari gorur. scripts/ BILEREK var: conarium-reconcile calisirken scripts/pg-snapshot.sql'e atif yapiyor, olmazsa kullanici destek maili yazar.",
|
|
5
5
|
"files": [
|
|
6
6
|
"dist",
|