cloakapi 0.5.1__tar.gz

cloakapi-0.5.1/CHANGELOG.md

@@ -0,0 +1,382 @@
+# Changelog
+
+All notable changes to the CloakAPI Python SDK are documented here.
+
+Format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
+This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+---
+
+## [0.5.1] — 2026-11-15
+
+### Fixed
+
+- A `thinking` block is sent byte for byte as written, with or without a
+  `signature`. The text and the signature are not replaced. The rules still
+  run over the thinking text. When they see personal data, the request carries
+  `unchecked_content` / `value_not_replaced` and the existing sentence, which
+  does not include the request text. A `redacted_thinking` block's `data` stays
+  as written and is named the same way when the rules match it. Thai and Khmer
+  text still carries `unchecked_content` / `unverified_script`. The send is not
+  stopped. Release 0.5.0 already left the block untokenised so a provider
+  signature still matched, and did not name personal data the rules saw in
+  that text.
+
+## [0.5.0] — 2026-11-12
+
+Part of release set R-1.6.1: every CloakAPI SDK of this set carries rule set
+1.6.1 and shares one behaviour contract. (0.4.1 was not offered for download.)
+
+### Added
+
+- `review=` on `CloakAPI` and `AsyncCloakAPI`: `review(text, info)` is called
+  with the exact outgoing body and a `ReviewInfo` (`state`, `coverage`,
+  `warnings`); return `True` to send.
+- Step form for applications with their own review screen:
+  `client.messages.prepare(...)` / `client.chat.completions.prepare(...)`,
+  `client.approve(prepared)`, `client.send(approved)`.
+- `coverage` and `warnings` on every reply; `client.last_warnings`.
+  A notice is a `SendWarning(code, reason, message)`; codes `reduced_coverage`
+  and `unchecked_content`.
+- `reply.receipt` and `client.last_receipt` (the receipt the gateway returned
+  with the reply, when it returned one; `last_receipt` is `None` after a
+  streaming call or a call that failed) and
+  `client.receipts.verify_offline(receipt, jwks=...)`.
+- Gateway refusals about the engine or the request proof carry the gateway's
+  code in `err.code` (`engine_identity_required`, `engine_outdated`,
+  `engine_untrusted`, `engine_superseded`, `pretokenised_required`) and one
+  sentence saying what it means and what to do.
+- Replies are restored in the string values of tool-call arguments as well as
+  in their text, including a stand-in split across streamed argument chunks
+  (chat `tool_calls` and Anthropic `input_json_delta`).
+- `cloakapi.engine_issue()`: why the engine is not in use, or `None`.
+- `examples/fake_gateway.py`: a stand-in gateway to run the hello world without a key.
+
+### Changed
+
+- The proof for the exact request bytes is requested on every send, also when
+  the structured rules prepared the request (0.4.1 skipped it there, and the
+  gateway does not relay a request without it). If the proof cannot be
+  obtained, the gateway or network error is raised and nothing is sent; 0.4.1
+  sent the request without proof in that case.
+- A request the structured rules prepared claims no engine: it carries no
+  `X-Cloak-Engine-Version` or `X-Cloak-Engine-Hash`. Coverage is stated in
+  `X-Cloak-Coverage` and in `X-CloakAPI-Tokenized: true;coverage=<coverage>`.
+- One rule for the engine pin. An engine file without `CLOAKAPI_ENGINE_SHA256_PIN`,
+  with a pin that does not match the loaded bytes, or built for another rule
+  set than this SDK is not used; the request goes out prepared by the
+  structured rules and the notice names what to fix. The engine inside a
+  platform wheel needs no pin of yours: the package knows which file it was
+  released with.
+- An engine that will not take a text (for example because its name model is
+  missing) no longer stops the request; the structured rules run instead, the
+  request then states no engine identity, and its notice says so
+  (`reduced_coverage` / `engine_refused`).
+- Content no longer stops a request. `RequestBodyRejectedError` was raised for
+  inline media and for a detected value in a tool schema `enum`, `const` or
+  `default`. Now: a detected value used as an object key in free-form data
+  is replaced, except a key under `metadata`, which stays as written while the
+  value under it is replaced (owner decision F-068); a value in a place that must stay as written
+  (tool schema literal or property name, key inside tool-call arguments,
+  identifier, number) is sent with `unchecked_content` / `value_not_replaced`;
+  images, audio and files in a request are sent as provided with
+  `unchecked_content` / `media_not_checked`. The notice reaches your review
+  before anything is sent. `RequestBodyRejectedError` remains for a request
+  that does not have the shape of a request.
+- A content block of a type this SDK does not name (for example `search_result`) is
+  sent. Every string in it outside protocol fields is tokenised, a string `source`
+  included (before, a string `source` was left as written), and the notice says so
+  (`unchecked_content` / `unrecognised_block`). A `redacted_thinking` block's `data`
+  (a provider blob) stays as written; before, it was handed to the tokeniser.
+- The engine file is hashed and compared before it is loaded. A truncated or
+  altered file is not loaded; the structured rules run and the notice names
+  the reason. (Before, the comparison came after loading and a truncated file
+  could end the process.)
+- Without the engine, the structured rules now apply every rule type of the
+  bundled rule set that has a pattern (139 of 142), with the check-digit
+  validation each rule names. Before, a hand-maintained table of 17 types ran,
+  so national ID numbers of most countries, postal codes, medical record
+  numbers and more were sent as written on that path. Names, places and
+  organisations still need the engine.
+- Coverage, notices, the restore map and the receipt belong to each request.
+  Overlapping requests on one client no longer take each other's notices.
+- `pip install` from the source archive or a checkout needs no flag
+  (`CLOAKAPI_ALLOW_PURE_WHEEL` is accepted and ignored). A wheel build accepts
+  only the engine file of the release set.
+- The package builds, tests and packs from its own directory.
+
+### Fixed
+
+- A reply that holds a `thinking`, `redacted_thinking`, `server_tool_use` or
+  other block type is read. Before, the reply model knew only text and
+  `tool_use` blocks, and such a reply failed with "Gateway returned an invalid
+  response". Thinking is kept exactly as the model wrote it: a reply never
+  restores it, and a thinking block sent back is no longer tokenised, so its
+  `signature` still matches. A `server_tool_use` block sent back is tokenised
+  like other blocks, with its tool name and id as written.
+- A reply could be restored to the engine's stand-in address instead of your
+  address: a second local pass replaced the stand-in again and the reply was
+  restored one step only.
+- The notice about reduced coverage now says why (missing or wrong pin, another
+  rule set, an engine file that cannot be loaded and the glibc version it needs).
+
+### Deprecated
+
+- `review_callback=` (receives a `RelayReview`). Use `review=`. Removed in 0.6.
+
+## [0.4.0] — 2026-08-09
+
+### Fixed — P0: the SDK silently protected 17 of 140 PII types off Linux/x86-64 (finding 180)
+
+`cloakapi` was published as a SINGLE `cloakapi-0.3.1-py3-none-any.whl` that
+bundled one `libcloak_engine.so` built for Linux/x86-64. On macOS (Intel and
+Apple Silicon), Windows and Linux/ARM that wheel installed **cleanly**, the
+library could not be loaded, and the SDK fell back to the pure-Python lane —
+**17 of the canonical 140 PII types**. The missing 123 include `NAME`,
+`GPS_COORDS`, every national-ID format, and the whole health/biometric family;
+they egressed **verbatim**. The only signal was an `engine="regex"` field that
+nothing read.
+
+A platform-tagged wheel would at least have made `pip` say "no matching
+distribution". `py3-none-any` removed even that.
+
+**Two changes, in the same direction:**
+
+- **Platform-specific wheels.** `hatch_build.py` (new hatchling build hook)
+  derives the wheel platform tag **from the bundled binary itself** — ELF/Mach-O/PE
+  header plus the glibc versions the object actually references — and **fails the
+  build** when a native library is present and no honest tag can be derived. An
+  `any`-tagged wheel containing a native library is now unbuildable. An
+  engine-less wheel additionally requires `CLOAKAPI_ALLOW_PURE_WHEEL=1`.
+  `scripts/build_wheels.py` builds one wheel per platform and prints every
+  platform it CANNOT build, with the reason.
+- **Fail-closed reduced lane.** `cloakapi/degraded.py` (new). Whenever the
+  native engine cannot be loaded, `tokenize_text_ex` / `tokenize_text`,
+  `client.detect.detect` and `prepare_attachments` now raise
+  `ReducedCoverageError` instead of quietly running reduced. Opt in with
+  `CLOAKAPI_ALLOW_REDUCED=1` (or `allow_reduced=True` at the call site) and you
+  get a `ReducedCoverageWarning` **and** an unconditional stderr banner — the
+  banner because `warnings` can be filtered process-wide, and a degradation a
+  stray filter can mute is the silence this fix exists to end.
+
+**Breaking for callers who were relying on the silent fallback** — deliberately.
+A privacy SDK that quietly protects less than it promises is worse than one that
+refuses to start.
+
+### Added
+
+- `cloakapi.ReducedCoverageError`, `ReducedCoverageWarning`, `coverage_counts()`,
+  `reduced_coverage_allowed()`, `guard_reduced_coverage()`, `ENV_ALLOW_REDUCED`.
+- `linux aarch64` engine build (Graviton, ARM servers, Docker on Apple Silicon):
+  `cloakapi-0.4.0-py3-none-manylinux_2_39_aarch64.whl`.
+
+### Known gaps (explicitly BLOCKED, not hidden)
+
+macOS (both arches), Windows (msvc and gnu) and musl/Alpine wheels cannot be
+built on the current builder; see the BLOCKED table in
+`goal-run/F-BEVIS/SAK180-PYTHON-SDK-ALLE-PLATTFORMER.md` and the `MATRIX` in
+`scripts/build_wheels.py`. Until those exist, users there install the sdist and
+hit the fail-closed error rather than silent 17-type protection.
+
+---
+
+## Earlier notes, not tied to a release
+
+These notes were written between 0.1.0 and 0.5.0 under an "Unreleased" heading
+and are kept as written. 0.4.1 was not offered for download. Where they describe
+a refusal, the 0.5.0 entry above says what replaced it: content no longer stops
+a request.
+
+### Fixed — refuse unprotected and unreviewable request egress
+
+- Sync and async relay calls now reject `tokenize=False` before transport,
+  require the pre-tokenized proof, walk the supported text-bearing request
+  slots, and refuse inline media or sensitive schema literals.
+- Requests and streams do not follow redirects. Upstream response text and
+  transport exception details are no longer copied into SDK errors or logs.
+- Invalid surrogate-mode diagnostics no longer retain or echo the caller's raw
+  value. The `messages.create` and chat completion docstrings describe which
+  body text is transformed and which unsafe values are refused.
+
+**Breaking behavior/API changes for release notes:** `tokenize=False` now raises
+`PlaintextRelayNotSupportedError`; `SurrogateModeError` no longer takes or
+exposes the raw invalid value; `NetworkError.cause` is always `None`; and API
+errors use status-based generic messages rather than upstream response text.
+These changes require a new SDK version before republishing. Do not republish
+the changed bytes under the existing `0.4.1` identity.
+
+### Fixed — fail closed on unavailable file engines and require review before attachment egress
+
+- File/image operations now explain which platform lacks a compatible
+  `libcloak_engine`, how to download or build one, and confirm that raw bytes
+  were not sent. `CLOAKAPI_ALLOW_REDUCED` remains text-only.
+- Runtime loading now refuses the withdrawn 6ed6, c135 (aarch64), and c965
+  engine digests that the wheel builder already rejects. Stale served wheels
+  therefore fail closed instead of using an obsolete embedded motor.
+- `attachments=` now raises `AttachmentReviewRequiredError` before any request.
+  Call `tokenize_file`, review its returned text, then relay that text in
+  `messages`.
+- This runtime and egress behavior is assigned Python SDK version **0.4.1**.
+  Build and publish are still required before users of the hosted 0.4.0 files
+  receive these changes.
+
+### Fixed — P0: street addresses egressed verbatim (2026-07-28)
+
+Continental-European addresses, which put the house number AFTER the street,
+were not detected and left this SDK in the clear: `Bergensgata 14`,
+`Storgata 5`, `Hauptstrasse 27`, `Rue de Rivoli 12`, `Via Roma 12`,
+`Calle Mayor 45`, `Herengracht 182`, `Mannerheimintie 12`. There were TWO
+independent leak paths, both real shipping configurations:
+
+- **FFI path (default).** `engine.py` resolves the bundled
+  `cloakapi/_lib/libcloak_engine.so` BEFORE the in-repo `target/release` build.
+  The bundled artifact was stale (pre-fix), so it kept leaking even after the
+  shared ruleset moved to 1.6.0 and the engine was correctly rebuilt — the
+  rebuild never reached the copy the SDK actually loads. The bundled engine has
+  been refreshed, and `tests/test_ruleset_binding.py` now fails if it ever goes
+  stale again.
+- **Pure-Python fallback.** `pii/patterns.py` had NO `ADDRESS` type at all, so it
+  leaked BOTH orderings — the Anglo forms were not "controls that kept working"
+  there either. `ADDRESS` is now **derived from the canonical ruleset** at import
+  time rather than hand-written, so it cannot drift from the fasit.
+
+### Fixed — engine identity was a hand-typed literal that had drifted
+
+`engine.RULESET_VERSION` was the literal `"1.4.29"` while the shared ruleset was
+at `1.6.0`. That value is emitted as `X-Cloak-Engine-Version`, which the
+gateway's EnforceEngineFloor gate (ADR 0014 §3) floor-checks — so the SDK
+declared a ruleset it was not running. Two tests asserted the literal and so
+PINNED the drift instead of catching it; both now assert the derived value.
+`RULESET_VERSION` is now read from `shared/pii-patterns/patterns.json` (bundled
+into the wheel as `cloakapi/_ruleset/patterns.json`, with a byte-identity guard).
+When no ruleset is readable the SDK reports `0.0.0-unknown` — a deliberately
+invalid sentinel so the gateway rejects rather than accepting a stale semver.
+
+> **Release note:** this changes runtime BEHAVIOUR without a version bump so far.
+> The published `0.1.1` artifact leaks these addresses; do not ship the fixed code
+> under the same version number.
+
+### Added — SDK parity (Phase 2c / Stage-1 A1-PYTHON)
+
+- **Hardened, byte-locked disclosure (C7).** New `cloakapi.disclosure` module:
+  `CLK_DISCLOSURE_TEXT` / `CLOAK_ANGLE_DISCLOSURE_TEXT` (embedded byte-for-byte,
+  sha256-checked against the conformance golden vectors), `disclosure_text`,
+  `detect_marker_format`, and `with_disclosure` (idempotent, fail-safe leading
+  `system` message). Replaces the stale, weak `CONTEXT_PREAMBLE`, which is now an
+  alias of the hardened `cloak-angle` disclosure (the `<<CLOAK:…>>` lane this SDK
+  emits).
+- **On-device device-receipt signer (C8).** `sign_device_receipt` +
+  `generate_device_key_pair` + `DeviceReceiptError` (ECDSA P-256, RFC-8785 JCS, raw
+  `r‖s` base64url). Content-free v3 receipts that `verify_device_receipt` validates
+  offline; fail-closed. `verify_device_receipt` added as the canonical alias.
+- **Privacy posture (C20).** `cloakapi.posture`: `privacy_posture`, `PrivacyPosture`,
+  `PRIVACY_TIERS` — engine identity + fail-closed + Level-1 tier introspection.
+
+### Changed
+
+- **Secrets are tokenise-and-flag, never blocked (C5).** Corrected stale
+  "hard-blocked secret" docstrings in `engine.py`, `pii/tokenizer.py`, and
+  `resources/detect.py`: a credential is tokenised to `<<CLOAK:CRED_KEY:…>>` and
+  flagged, never thrown/blocked.
+- Bundled `cloakapi/_lib/libcloak_engine.so` refreshed to the FROZEN engine
+  (sha256 `9e8bab7c…`, ruleset `03597feb`, v1.4.29) so the shipped wheel attests the
+  correct `X-Cloak-Engine-Hash` out of the box.
+- Documented the browser-only capabilities (C4 caption gate, C5 review UI) as
+  intentionally not shipped server-side.
+
+### Tests
+
+- `tests/test_conformance_golden.py` — asserts the 14 FFI exact vectors, the
+  disclosure byte-lock + `with_disclosure` behaviour, the receipt fixture + tamper
+  case, and a self-minted receipt round-trip against
+  `goal-run/conformance/golden-vectors.json`. **CONFORMANT.**
+
+---
+
+## [0.1.0] - 2026-04-18
+
+### Added
+
+#### Core SDK
+- `CloakAPI` synchronous client with `messages`, `chat`, `buffer`, `admin` resource namespaces
+- `AsyncCloakAPI` asynchronous client with identical surface area using `httpx.AsyncClient`
+- Both clients support context manager (`with` / `async with`) usage
+- `http_client` constructor parameter to inject a pre-configured `httpx.Client` / `httpx.AsyncClient`
+
+#### Anthropic-compatible messages
+- `client.messages.create(model, messages, ...)` returning a typed `Message` Pydantic model
+- `stream=True` mode returning `Iterator[StreamEvent]` / `AsyncIterator[StreamEvent]`
+- Typed streaming events: `MessageStart`, `ContentBlockStart`, `ContentBlockDelta`,
+  `ContentBlockStop`, `MessageDelta`, `MessageStop`, `ErrorEvent`
+
+#### OpenAI-compatible chat completions
+- `client.chat.completions.create(model, messages, ...)` returning typed `ChatCompletion`
+- `stream=True` mode returning `Iterator[ChatCompletionChunk]` / `AsyncIterator[ChatCompletionChunk]`
+
+#### Buffered responses
+- `client.buffer.get(request_id)` returning `BufferedResponse`
+
+#### Admin stats (admin token required)
+- `client.admin.stats.overview()` → `AdminOverview`
+- `client.admin.stats.usage(period=...)` → `AdminUsagePeriod`
+- `client.admin.stats.users(page=..., per_page=...)` → `AdminUsers`
+
+#### PII tokenization
+- `tokenize=True` on the client or per-call enables automatic PII detection and tokenization
+- Supported types: EMAIL, PHONE, SSN, IBAN, CREDIT_CARD, IP_ADDRESS, IPV6_ADDRESS,
+  DATE_OF_BIRTH, PASSPORT, URL, API_KEY
+- `X-CloakAPI-Tokenized: true` header set automatically when tokenization is active
+- Token format: `<<CLOAK:{TYPE}:{6-char-hash}>>`
+- Deterministic tokens: same PII value always maps to the same token within a session
+- Response content is automatically de-tokenized before returning to the caller
+- `extra_patterns` parameter in `detect_pii()` for user-supplied regex patterns
+- Existing tokenized regions skipped (no double-tokenization)
+
+#### Error handling
+- Full exception hierarchy: `CloakAPIError` → `APIError` → specific typed errors
+- `RateLimitError` with `retry_after` attribute
+- `ConcurrencyLimitError` for streaming limit (code=`stream_concurrency_limit`)
+- `NetworkError` wraps connection/timeout failures with `.cause` attribute
+
+#### Retry logic
+- Automatic retry on: 429, 502, 503, 504, `httpx.ConnectError`, `httpx.ReadTimeout`
+- Exponential backoff with full jitter
+- Respects `Retry-After` response header for 429
+- Configurable via `max_retries` constructor argument (default: 3)
+- Non-retryable 4xx errors (401, 403, 404, etc.) raise immediately
+
+#### Configuration
+- Priority: constructor arg → `CLOAKAPI_API_KEY` env → `~/.cloakapi/config.json`
+- `CLOAKAPI_BASE_URL` env var supported
+- `_load_config_file()` / `_save_config_file()` utilities for config management
+
+#### Logging
+- `logging.getLogger("cloakapi")` — API key is scrubbed in all log messages
+- `CLOAKAPI_LOG_REQUESTS=1` env var enables request-level debug logging
+
+#### CLI (`cloakapi` entry point)
+- `cloakapi ping` — verify API key validity and gateway connectivity
+- `cloakapi chat --model ... --prompt ...` — one-shot Anthropic-format chat
+- `cloakapi stream --model ... --prompt ...` — streaming chat demo
+- `cloakapi config show` — display current credentials (masked)
+- `cloakapi config set --api-key ... --base-url ...` — save credentials
+
+#### Packaging
+- `pyproject.toml` (PEP 621, hatchling build backend)
+- `py.typed` marker for PEP 561 compliance
+- Dependencies: `httpx>=0.27`, `pydantic>=2.5`, `typer>=0.12`, `rich>=13`
+- Optional extras: `[ner]` (spaCy), `[gliner]` (GLiNER ONNX)
+- `noxfile.py` for multi-Python test matrix (3.10–3.14)
+- `ruff` for linting and formatting
+- `mypy --strict` for type checking
+
+#### Testing
+- pytest suite with `respx` mocking (no real HTTP calls in default suite)
+- Integration tests gated behind `CLOAKAPI_INTEGRATION=1` env var
+- PII tokenizer golden tests: email, phone, SSN, IBAN, credit card, IPv4, IPv6
+- Streaming parser tests with byte-for-byte canned SSE responses
+- Retry logic tests (429+Retry-After, 503×3, non-retryable 401)
+- CLI tests via `typer.testing.CliRunner`
+- Config resolution tests with `monkeypatch`
+- `≥85%` line coverage target
+

cloakapi-0.5.1/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2024-2026 Klokk Nettablering
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

cloakapi-0.5.1/NOTICE

@@ -0,0 +1,18 @@
+CloakAPI SDK for Python
+Copyright 2024-2026 Klokk Nettablering (org. no. 821 466 962, Norway)
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).
+
+This package includes the CloakAPI rule set under the same license.
+Where a build also ships a compiled engine, that binary is under the
+same license. The engine's source code is not distributed with this package.
+
+"CloakAPI" and "Verified by CloakAPI" are trademarks of Klokk Nettablering.
+The Apache License does not grant permission to use them (section 6);
+see TRADEMARKS.md.
+
+This product includes third-party software and data. Their notices and
+license texts are in THIRD-PARTY-NOTICES.md and the licenses/ directory.
+Place names are derived from GeoNames (https://www.geonames.org/), licensed
+under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/); modified by
+filtering and compaction.