codeimprint 0.5.0a12__tar.gz → 0.5.0a13__tar.gz

{codeimprint-0.5.0a12 → codeimprint-0.5.0a13}/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 0.5.0a13 — The old brand name is gone [CIM-BE-26-v1]
+
+- **Development origin:** `receipt.ORIGIN`, the development log origin the tests' simulated
+  server uses, is now `codeimprint.dev/log/v1`, as in engine 0.7.0a18. Verification still takes
+  whatever origin a log publishes, so nothing changes for users. The name `ORIGIN` stays.
+- **Media type:** `docs/imprint-format.md` names `application/vnd.codeimprint.imprint+json`.
+- **History:** the changelog no longer names the old brand or its domain.
+- **Guard:** `tests/test_no_legacy_brand.py` fails if the old name appears anywhere in the tree.
+
 ## 0.5.0a12 — Licensed under Apache-2.0 [CIM-BE-23-v1]
 
 - Licensed under Apache-2.0. Copyright 2026 Elystra Private Limited.
@@ -14,7 +23,7 @@
     wheel and the sdist.
 - The PyPI page no longer mentions the dropped `code-imprint` alias.
 - Elystra Private Limited is the legal owner. It is the PyPI author and maintainer, with
-  `dev@elystratech.com`. The product is "CodeImprint", not "CodeImprint by Mudrika", in
+  `dev@elystratech.com`. The product is "CodeImprint", without the old brand line, in
   the READMEs, the PyPI description, `imprint --help` and the workflow `imprint init`
   writes.
 
@@ -84,8 +93,8 @@ Packaging [CIM-BE-20-v1]: the client's first PyPI release.
   the user config (`hubs`). With none known, no link or badge is printed, only
   `imprint verify <file>`; never a localhost guess. A localhost hub is kept only from a
   localhost server, and any other hub only over HTTPS.
-- **Changed:** `CODEIMPRINT_PUBLIC_URL`, the saved `public_url` and the `https://mudrika.io`
-  default are no longer used; `imprint login --public-url` is accepted but ignored, with a
+- **Changed:** `CODEIMPRINT_PUBLIC_URL`, the saved `public_url` and the old
+  default public URL are no longer used; `imprint login --public-url` is accepted but ignored, with a
   warning. The terms hint names the hub's account page when the hub is known.
 - `imprint verify` with no target checks `.imprint/baseline.imprint` in the current folder;
   without one, the usual usage error.
@@ -211,7 +220,7 @@ Packaging [CIM-BE-20-v1]: the client's first PyPI release.
 ## Unreleased [CI-BE-7-v1]
 
 - Public-URL setting for badge and verify links: `CODEIMPRINT_PUBLIC_URL`, or
-  `imprint login --public-url URL` (saved in the user config). Default `https://mudrika.io`;
+  `imprint login --public-url URL` (saved in the user config). Default: the old development domain;
   launch value `https://app.codeimprint.ai`.
 - The log origin is no longer fixed in the client: a checkpoint must carry its receipt's
   origin, and with `--online` the live log must still have it. Servers can now run under
@@ -249,7 +258,7 @@ Packaging [CIM-BE-20-v1]: the client's first PyPI release.
   against its published keys (trusted on first use, then only ever extended), signs the
   digest locally, uploads the signature, and saves `.imprint/baseline.receipt.json` and
   `.imprint/server-keys.json` next to the Imprint. It prints the log entry, timestamp status,
-  badge and `https://mudrika.io/i/<ID>`. In CI every failure after the upload is a warning.
+  badge and `<public URL>/i/<ID>`. In CI every failure after the upload is a warning.
 - `imprint verify <file|receipt|ID>` checks digest, attestation, developer signature, log
   inclusion, RFC 3161 timestamp and time order offline, one `PASS`/`WARN`/`FAIL` line each;
   `--online` adds log consistency, entry order and the public record; `--keys FILE` pins

{codeimprint-0.5.0a12 → codeimprint-0.5.0a13}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: codeimprint
-Version: 0.5.0a12
+Version: 0.5.0a13
 Summary: CodeImprint: seal your code with a CodeImprint server (tamper-evident, logged and timestamped) and verify seals offline.
 Project-URL: Homepage, https://codeimprint.ai
 Project-URL: Hub, https://app.codeimprint.ai

{codeimprint-0.5.0a12 → codeimprint-0.5.0a13}/pyproject.toml

@@ -6,7 +6,7 @@ build-backend = "hatchling.build"
 # Published on PyPI as `codeimprint`. The import package stays `codeimprint_cli` and the
 # command `imprint`.
 name = "codeimprint"
-version = "0.5.0a12"
+version = "0.5.0a13"
 description = "CodeImprint: seal your code with a CodeImprint server (tamper-evident, logged and timestamped) and verify seals offline."
 readme = "README.pypi.md"
 license = "Apache-2.0"

{codeimprint-0.5.0a12 → codeimprint-0.5.0a13}/src/codeimprint_cli/__init__.py

@@ -5,4 +5,4 @@ A thin client for a CodeImprint server: it zips a project, asks the server to se
 it, and verifies Imprint files offline. All analysis happens on the server.
 """
 
-__version__ = "0.5.0a12"
+__version__ = "0.5.0a13"

{codeimprint-0.5.0a12 → codeimprint-0.5.0a13}/src/codeimprint_cli/receipt.py

@@ -17,7 +17,7 @@ from .imprint_file import b64d, canonical
 
 # The development log's origin. Servers can run under another origin (CODEIMPRINT_LOG_ORIGIN),
 # so a checkpoint must carry its receipt's origin, and the live log must keep it.
-ORIGIN = "codeimprint.mudrika.io/log/v1"
+ORIGIN = "codeimprint.dev/log/v1"
 CLOCK_SKEW = timedelta(minutes=5)       # allowed between the server's and a TSA's clock
 CONFIRM_WITHIN = timedelta(hours=1)     # a TSA time further after the seal is reported
 AGREE_WITHIN = timedelta(hours=1)       # valid tokens of one subject further apart: FAIL