@conarium-ai/core 0.2.34 → 0.2.35
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 +26 -0
- package/README.md +9 -0
- package/docs/claims/reviews/0.2.35.md +65 -0
- package/docs/security/NPM-PROVENANCE.md +10 -3
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,31 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.2.35 — 2026-08-20 — two sentences that our own actions made false
|
|
4
|
+
|
|
5
|
+
Nothing in the engine changed. This release exists because publishing 0.2.34
|
|
6
|
+
invalidated a paragraph inside 0.2.34, which is a small thing that says something
|
|
7
|
+
about how documentation ages here.
|
|
8
|
+
|
|
9
|
+
- **`docs/security/NPM-PROVENANCE.md` said the full publish path had not run
|
|
10
|
+
yet.** It ran a few hours later, publishing 0.2.34 itself. The page now
|
|
11
|
+
separates the two histories: 0.2.33 carries a tarball and an attestation and no
|
|
12
|
+
bill of materials, because its artefacts were attached by the mode that skips
|
|
13
|
+
that step; 0.2.34 carries all three because the full path produced them. The
|
|
14
|
+
paragraph ends by pointing at the release page rather than at itself, which is
|
|
15
|
+
the only version of this sentence that does not expire.
|
|
16
|
+
- **The OpenSSF Best Practices badge is in the README, with what it is not.**
|
|
17
|
+
The project earned the passing badge on 2026-08-19 (project 14160, 64 of 67
|
|
18
|
+
criteria met, 3 not applicable and stated as such). The README says in the same
|
|
19
|
+
breath that this is self-certification rather than an audit, that the answers
|
|
20
|
+
are public and checkable, and that the Scorecard badge beside it carries a
|
|
21
|
+
`Code-Review` score of 0 because pull requests here are merged without a second
|
|
22
|
+
approver. A badge added without that sentence would be the kind of claim this
|
|
23
|
+
package spends its time refusing.
|
|
24
|
+
- One criterion was corrected before it was submitted rather than after: the
|
|
25
|
+
first answer for "the test suite covers most of the code" asserted coverage
|
|
26
|
+
that had never been measured. It now describes what is exercised and says the
|
|
27
|
+
ratio is not reported.
|
|
28
|
+
|
|
3
29
|
## 0.2.34 — 2026-08-19 — the prior-art claim that got narrower
|
|
4
30
|
|
|
5
31
|
A comparative claim in this package was too strong, and the correction came from
|
package/README.md
CHANGED
|
@@ -7,6 +7,7 @@
|
|
|
7
7
|
<a href="https://www.npmjs.com/package/@conarium-ai/core"><img src="https://img.shields.io/npm/v/@conarium-ai/core?style=for-the-badge" alt="npm" /></a>
|
|
8
8
|
<a href="https://github.com/dogrucanemek-alt/conarium/actions/workflows/security.yml"><img src="https://img.shields.io/github/actions/workflow/status/dogrucanemek-alt/conarium/security.yml?branch=main&style=for-the-badge&label=CI" alt="CI" /></a>
|
|
9
9
|
<a href="https://securityscorecards.dev/viewer/?uri=github.com/dogrucanemek-alt/conarium"><img src="https://api.securityscorecards.dev/projects/github.com/dogrucanemek-alt/conarium/badge" alt="OpenSSF Scorecard" /></a>
|
|
10
|
+
<a href="https://www.bestpractices.dev/projects/14160"><img src="https://www.bestpractices.dev/projects/14160/badge" alt="OpenSSF Best Practices" /></a>
|
|
10
11
|
<a href="https://conarium.dev"><img src="https://img.shields.io/badge/Website-conarium.dev-5a8cff?style=for-the-badge" alt="Website" /></a>
|
|
11
12
|
<a href="https://github.com/dogrucanemek-alt/conarium/blob/main/LICENSE"><img src="https://img.shields.io/badge/License-MIT-f2d79a?style=for-the-badge" alt="License" /></a>
|
|
12
13
|
<img src="https://img.shields.io/badge/Status-Early%20Access-ff6f80?style=for-the-badge" alt="Early Access" />
|
|
@@ -692,6 +693,14 @@ per-user identity bound to an identity provider rather than an operator token ma
|
|
|
692
693
|
and coverage declarations are yours to show your own auditor, and whether they
|
|
693
694
|
satisfy a given audit is between you and that auditor. If we ever hold your
|
|
694
695
|
data, or an engagement turns on the certificate itself, this line changes first.
|
|
696
|
+
- **The OpenSSF Best Practices badge above is self-certification, not an audit.**
|
|
697
|
+
We answered its 67 questions and published the answers; anyone can read them at
|
|
698
|
+
[project 14160](https://www.bestpractices.dev/projects/14160) and check each one
|
|
699
|
+
against this repository. That is worth something — the answers are falsifiable —
|
|
700
|
+
and it is not the same thing as someone independent having looked. Three of the
|
|
701
|
+
67 are marked not-applicable and say why. The Scorecard badge beside it is
|
|
702
|
+
machine-measured and includes a `Code-Review` score of 0, because pull requests
|
|
703
|
+
here are merged without a second approver.
|
|
695
704
|
|
|
696
705
|
Known gaps: [LIMITATIONS.md](LIMITATIONS.md), the README above,
|
|
697
706
|
[`docs/RECEIPT-SPEC.md`](docs/RECEIPT-SPEC.md),
|
|
@@ -0,0 +1,65 @@
|
|
|
1
|
+
# Claims review — 0.2.35
|
|
2
|
+
|
|
3
|
+
- base: v0.2.34
|
|
4
|
+
- head: ee31d7b
|
|
5
|
+
- surface: sha256:ad95f3ab81fa4cd74ce025a76e3cc9095ecbc5bfefaace3eec763e809eb7d02b
|
|
6
|
+
- verdict: pass
|
|
7
|
+
- reviewer: Claude (Opus 5)
|
|
8
|
+
|
|
9
|
+
Two surfaces changed: `README.md` and `docs/security/NPM-PROVENANCE.md`. Both
|
|
10
|
+
changes are corrections of claims that this project's own actions falsified
|
|
11
|
+
within hours, which is the pattern worth recording more than the diff.
|
|
12
|
+
|
|
13
|
+
## Findings
|
|
14
|
+
|
|
15
|
+
### 1. docs/security/NPM-PROVENANCE.md — corrected, and the correction is the release
|
|
16
|
+
|
|
17
|
+
- Claim, as of 0.2.34: *"The full path, producing all three, has not run yet."*
|
|
18
|
+
- Mechanism: the workflow runs and the release pages.
|
|
19
|
+
- Why it fell short: it was true when written and false a few hours later,
|
|
20
|
+
because publishing 0.2.34 ran that path. Verified from the destination: run
|
|
21
|
+
`32298849184` completed every step including the bill of materials; the
|
|
22
|
+
`v0.2.34` release page carries `conarium-ai-core-0.2.34.tgz` (764,893 bytes),
|
|
23
|
+
`.cdx.json` (70,245) and `.tgz.intoto.jsonl` (11,032); the tarball's sha512
|
|
24
|
+
matches the registry's `dist.integrity`; `gh attestation verify` returns 0.
|
|
25
|
+
- Disposition: rewritten to separate the two histories — 0.2.33 has two assets
|
|
26
|
+
because its artefacts came from the mode that skips the SBOM, 0.2.34 has three
|
|
27
|
+
— and to end by pointing at the release page rather than at itself. That is
|
|
28
|
+
the only form of the sentence with no expiry date.
|
|
29
|
+
- Note on the class: this is the second time in two releases that a sentence
|
|
30
|
+
about what *has not happened yet* went stale. The first was caught by an
|
|
31
|
+
external reviewer, this one by knowing to look. A statement of that shape
|
|
32
|
+
should carry the thing that answers it, not the answer.
|
|
33
|
+
|
|
34
|
+
### 2. README.md — a badge, and what it is not, in the same paragraph
|
|
35
|
+
|
|
36
|
+
- Claim: the OpenSSF Best Practices badge is displayed in the badge row.
|
|
37
|
+
- Mechanism: `bestpractices.dev` project 14160 — a **self-certification**
|
|
38
|
+
questionnaire, not an assessment by anyone else.
|
|
39
|
+
- Why it could fall short: a badge in a row of badges reads as certification. The
|
|
40
|
+
Scorecard badge beside it is machine-measured; this one is us answering 67
|
|
41
|
+
questions about ourselves.
|
|
42
|
+
- Disposition: added with the qualification attached rather than in a footnote —
|
|
43
|
+
self-certification not an audit, answers public and falsifiable at project
|
|
44
|
+
14160, 3 of 67 marked not applicable with reasons, and the neighbouring
|
|
45
|
+
Scorecard `Code-Review` score of 0 named in the same paragraph. Accepted.
|
|
46
|
+
|
|
47
|
+
### 3. The badge answers themselves — one corrected before submission
|
|
48
|
+
|
|
49
|
+
- Claim: the `test_most` criterion was first answered by asserting the test suite
|
|
50
|
+
covers most of the code.
|
|
51
|
+
- Mechanism: a coverage measurement.
|
|
52
|
+
- Why it fell short: coverage is not reported as a percentage in this project,
|
|
53
|
+
so the assertion had nothing behind it. It was an easy sentence to write and
|
|
54
|
+
nobody outside would have checked it.
|
|
55
|
+
- Disposition: rewritten before the form was submitted to describe what is
|
|
56
|
+
exercised — the policy gate, masking, the receipt chain and verifier, the
|
|
57
|
+
reconciliation tool, every documented CLI surface, and the documented quickstart
|
|
58
|
+
on three Node majors — and to say the ratio is not measured. Recorded here
|
|
59
|
+
because the badge answers are a claim surface that lives outside this
|
|
60
|
+
repository and no gate here can see them.
|
|
61
|
+
|
|
62
|
+
## What did not change
|
|
63
|
+
|
|
64
|
+
The engine, the receipt format, the policy gate, the reconciliation tool and the
|
|
65
|
+
conformance vectors are untouched. `run-checks` and the suite pass unchanged.
|
|
@@ -79,10 +79,17 @@ rather than the release. Its sha512 is checked against the registry's
|
|
|
79
79
|
the workflow's `artefacts` mode — a dispatch that attaches files to a version
|
|
80
80
|
already on npm and skips publishing, tagging and the registry entirely. It was
|
|
81
81
|
run against **0.2.33**, whose release page had been left empty when that version
|
|
82
|
-
shipped. So 0.2.33 carries the tarball and the attestation and
|
|
82
|
+
shipped. So **0.2.33 carries the tarball and the attestation and no bill of
|
|
83
83
|
materials**: that step is skipped in artefacts mode, because the lockfile in the
|
|
84
|
-
tree belongs to a later version.
|
|
85
|
-
|
|
84
|
+
tree belongs to a later version.
|
|
85
|
+
|
|
86
|
+
The full path, producing all three, first ran for **0.2.34** later the same day.
|
|
87
|
+
Its release page carries the tarball, the CycloneDX bill of materials and the
|
|
88
|
+
attestation, and the tarball's sha512 matches the registry's `dist.integrity`.
|
|
89
|
+
|
|
90
|
+
Which means the table above describes two different histories depending on the
|
|
91
|
+
version you are holding, and the release page — not this document — is what
|
|
92
|
+
answers for any particular one.
|
|
86
93
|
|
|
87
94
|
⛔ **The `gh` command below works only for versions whose release page actually
|
|
88
95
|
carries the `.intoto.jsonl` asset** — check the page, do not assume from the
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@conarium-ai/core",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.35",
|
|
4
4
|
"mcpName": "io.github.dogrucanemek-alt/conarium",
|
|
5
5
|
"//files-artefakt": "examples/ altindaki uretilmis dosyalar (ozel anahtar, makbuz/denetim JSONL) ELENIR. .gitignore npm'i baglamaz: izin listesinde 'examples' oldugu icin demoyu kosturmus bir makinede 'npm publish' _keys/audit-ed25519.pem'i (OZEL ANAHTAR) ve makbuzlari yayinliyordu. test/pack_artefakt.mjs bunu kilitler. Elemeler examples/ ile SINIRLI: test-vectors/ altindaki receipts.jsonl ve .pub.pem YAYINLANMAK ZORUNDA, yoksa ucuncu taraf konformans vektorlerini kosturamaz.",
|
|
6
6
|
"//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.",
|