cloakapi 1.4.1-x86_64-linux
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.
- checksums.yaml +7 -0
- data/CHANGELOG.md +160 -0
- data/LICENSE +202 -0
- data/NOTICE +18 -0
- data/README.md +407 -0
- data/THIRD-PARTY-NOTICES.md +22 -0
- data/TRADEMARKS.md +19 -0
- data/examples/fake_gateway.rb +78 -0
- data/examples/hello.rb +64 -0
- data/lib/cloakapi/_lib/linux-x86_64/libcloak_engine.so +0 -0
- data/lib/cloakapi/client.rb +1272 -0
- data/lib/cloakapi/degraded.rb +77 -0
- data/lib/cloakapi/disclosure.rb +252 -0
- data/lib/cloakapi/engine.rb +702 -0
- data/lib/cloakapi/errors.rb +65 -0
- data/lib/cloakapi/pii/bundled_rules.rb +670 -0
- data/lib/cloakapi/pii/card_spans.rb +300 -0
- data/lib/cloakapi/pii/detector.rb +1925 -0
- data/lib/cloakapi/pii/patterns.json +2238 -0
- data/lib/cloakapi/pii/pii_match.rb +7 -0
- data/lib/cloakapi/pii/pii_type.rb +7 -0
- data/lib/cloakapi/pii/ruleset.rb +65 -0
- data/lib/cloakapi/pii/tokenizer.rb +411 -0
- data/lib/cloakapi/posture.rb +82 -0
- data/lib/cloakapi/receipts.rb +406 -0
- data/lib/cloakapi/resources/chat.rb +82 -0
- data/lib/cloakapi/resources/messages.rb +90 -0
- data/lib/cloakapi/resources/models.rb +25 -0
- data/lib/cloakapi/resources/receipts.rb +162 -0
- data/lib/cloakapi/resources/reconstruct.rb +120 -0
- data/lib/cloakapi/resources/request_strings.rb +485 -0
- data/lib/cloakapi/resources/reviewable.rb +163 -0
- data/lib/cloakapi/resources/tokens.rb +28 -0
- data/lib/cloakapi/routing/bundled-catalogue.json +107 -0
- data/lib/cloakapi/routing.rb +500 -0
- data/lib/cloakapi/streaming.rb +196 -0
- data/lib/cloakapi/surrogate_mode.rb +233 -0
- data/lib/cloakapi/version.rb +15 -0
- data/lib/cloakapi/warnings.rb +137 -0
- data/lib/cloakapi.rb +37 -0
- data/licenses/Apache-2.0.txt +202 -0
- data/licenses/CC-BY-4.0.txt +104 -0
- data/licenses/MIT-Faker.txt +21 -0
- data/licenses/MIT.txt +21 -0
- metadata +150 -0
checksums.yaml
ADDED
|
@@ -0,0 +1,7 @@
|
|
|
1
|
+
---
|
|
2
|
+
SHA256:
|
|
3
|
+
metadata.gz: 2c6a709962cb4f527d0cb28ef91a9daf00bd4fcadd93c035b90611d65de6a889
|
|
4
|
+
data.tar.gz: b3c0acb7fc0765f53def1c70cfd37bc7061a2215bdd3cbfae0662c072cf96136
|
|
5
|
+
SHA512:
|
|
6
|
+
metadata.gz: e2cb3a7971650b3adcaba546b29e53322b408a3106aadaf3daec6cad0a2b36fefadc19da1abda05275a5a5e1c2aba707de3fe5871928b9a2535af7cd0df672e6
|
|
7
|
+
data.tar.gz: 5aca4df41a7657a3428392e45162f4ac479351b3a5314885d8e47f3cbec56b8450497df00b6210a38b566dc2bf357fc50fa9b00ddd8aafd34f8a48f2337e027f
|
data/CHANGELOG.md
ADDED
|
@@ -0,0 +1,160 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
All notable changes to the `cloakapi` gem. Versions follow semantic versioning.
|
|
4
|
+
|
|
5
|
+
## 1.4.1
|
|
6
|
+
|
|
7
|
+
Part of release set R-1.6.1 (rule set 1.6.1).
|
|
8
|
+
|
|
9
|
+
### Changed behaviour
|
|
10
|
+
|
|
11
|
+
- A device receipt whose `token_binding_hmac` is empty, or the SHA-256 of the empty string, still verifies. The result says that no token binding was committed. The signature is not rejected and is not counted as proof.
|
|
12
|
+
- A request prepared without an engine hash still sends `X-Cloak-Engine-Hash-Status: unavailable` and still omits `X-Cloak-Engine-Version` and `X-Cloak-Engine-Hash`. That is the same wire as the TypeScript SDK. The status is not an engine identity.
|
|
13
|
+
|
|
14
|
+
## 1.4.0
|
|
15
|
+
|
|
16
|
+
Part of release set R-1.6.1 (rule set 1.6.1).
|
|
17
|
+
|
|
18
|
+
### Changed behaviour
|
|
19
|
+
|
|
20
|
+
- **Thinking is sent back as the model wrote it.** A `thinking` block in a request
|
|
21
|
+
was tokenised like other text, so a value the model wrote in its thinking was
|
|
22
|
+
replaced and the text no longer matched its `signature`; and a stand-in the
|
|
23
|
+
model repeated there stopped the request ("reserved token marker in request").
|
|
24
|
+
A `thinking` or `redacted_thinking` block now goes out exactly as received, and
|
|
25
|
+
a reply never restores thinking, so it holds stand-ins only. The reply now also
|
|
26
|
+
restores the input of a `tool_use` or `server_tool_use` block, as the other
|
|
27
|
+
SDKs do; sent back, that input is tokenised again.
|
|
28
|
+
- **A request with tools, `tool_choice` or `response_format` is sent.** A string under a
|
|
29
|
+
key named `type` anywhere in the request was read as a content-block type, so a tool's
|
|
30
|
+
JSON Schema (`"type": "object"`), `tool_choice: { type: "auto" }`,
|
|
31
|
+
`response_format: { type: "json_object" }` and a metadata field named `type` raised
|
|
32
|
+
`ArgumentError: unknown content block type` before anything was sent. Only a message's
|
|
33
|
+
content array is checked for block types now; other `type` values are handled like any
|
|
34
|
+
other string.
|
|
35
|
+
- **A content block of a type this SDK does not name is sent.** Every string in it is
|
|
36
|
+
tokenised like other text; protocol fields (`type`, `id`, a thinking block's
|
|
37
|
+
`signature`, `cache_control`) and a media `source` object stay as written; and the
|
|
38
|
+
request carries `unchecked_content` / `unrecognised_block`. Before,
|
|
39
|
+
`RequestStrings.sanitize` raised `ArgumentError: unknown content block; refusing to
|
|
40
|
+
send unreviewed structure`, which also stopped `thinking` and `redacted_thinking`
|
|
41
|
+
blocks carried into a later request. Those two are named now: the thinking text is
|
|
42
|
+
tokenised, the signature and the redacted data stay as written. A string `source`
|
|
43
|
+
(the citation source of a search result) is text, not media.
|
|
44
|
+
- **A key named `content` inside data is data.** `content` holds content blocks
|
|
45
|
+
only on a message and inside a block that carries content (`tool_result`,
|
|
46
|
+
`search_result`, a server tool result); `system` only at the top level; `messages`
|
|
47
|
+
and `tools` only at the top level and `tool_calls` only on a message. Anywhere else
|
|
48
|
+
(tool input, metadata, any JSON the caller nests) such a key is ordinary data and
|
|
49
|
+
its strings are tokenised. Before, `{"content": ["text"]}` in a tool's input or in
|
|
50
|
+
metadata raised `ArgumentError: content blocks must be objects`, and a key named
|
|
51
|
+
`file` or `image_url` there was sent as written as media.
|
|
52
|
+
- **The text of a plain-text document is tokenised.** A `document` block whose
|
|
53
|
+
`source` has `"type": "text"` (or `"content"`, a list of content blocks) is text,
|
|
54
|
+
not media: its data is tokenised like other text. Before, every `source` object
|
|
55
|
+
was taken for media, so that text was sent as written with `media_not_checked`.
|
|
56
|
+
Images, audio and files as base64 bytes, URLs or file ids are still sent as
|
|
57
|
+
provided, with `media_not_checked`.
|
|
58
|
+
- **The built-in rules run every rule type of the bundled rule set** that has
|
|
59
|
+
a pattern (139 of 142; NAME, PLACE and ORGANIZATION need the name model),
|
|
60
|
+
with their check digits and the rule set's precedence order, in addition to
|
|
61
|
+
what they recognised before. On the shared vector file of the rules lane
|
|
62
|
+
(`sdk/conformance/rules-lane-vectors.json`) the rule-set runner gives exactly
|
|
63
|
+
the reference detections on all 1,166 exact vectors and answers all 621
|
|
64
|
+
check-digit rows as the reference does. Without the engine, Norwegian and
|
|
65
|
+
other national ID numbers, phone numbers outside the US format, postcodes and
|
|
66
|
+
plain dates of birth are now replaced. Stand-ins for these carry the labels
|
|
67
|
+
the engine uses (`ID_GOV`, `CONTACT_PH`, `GEO_ZIP`, `PII_DOB`, ...); values the
|
|
68
|
+
rules already recognised keep their stand-ins. Two rule types also replace
|
|
69
|
+
things that are not personal data (any date; long runs of digits). A short
|
|
70
|
+
message takes about 1 ms instead of 0.1 ms, 50 kB about 0.5 s instead of
|
|
71
|
+
0.03 to 0.3 s.
|
|
72
|
+
- **A wrong or missing engine pin no longer stops a request.** If
|
|
73
|
+
`CLOAKAPI_ENGINE_SHA256_PIN` is missing, malformed or not the SHA-256 of the
|
|
74
|
+
file at `CLOAKAPI_ENGINE_LIB`, or the engine file is missing, cannot be loaded
|
|
75
|
+
or is built for another rule set, the engine is not used and the request is
|
|
76
|
+
prepared by the built-in rules, with a warning that names the reason. Before,
|
|
77
|
+
several of these raised `CloakAPI::Engine::EngineError`. An engine without a
|
|
78
|
+
pin is not used; before, an unpinned engine found on disk could be loaded.
|
|
79
|
+
- **File tokenisation tells the engine that reduced coverage is accepted**
|
|
80
|
+
under the standard policy (the same `accepted` flag the text path, the PHP
|
|
81
|
+
SDK and the Java SDK send). With the pinned engine and no name model the
|
|
82
|
+
file is still tokenised and a warning is written. Strict mode
|
|
83
|
+
(`allow_reduced_coverage: false` or `strict_coverage: true`) still refuses
|
|
84
|
+
that file. Before, the flag never reached the engine, which answered with
|
|
85
|
+
code 5 and the file was not tokenised.
|
|
86
|
+
- **Text the loaded engine cannot process** is handled by the built-in rules
|
|
87
|
+
with a warning instead of raising `EngineError`. (Files still need the engine.)
|
|
88
|
+
- **A request prepared without the engine states no engine identity.** It
|
|
89
|
+
carries `X-CloakAPI-Tokenized: true;coverage=rules_only` and neither
|
|
90
|
+
`X-Cloak-Engine-Version` nor `X-Cloak-Engine-Hash`; before, the version header
|
|
91
|
+
was always sent. Today's gateway answers such a request with HTTP 428.
|
|
92
|
+
- **Overlapping detected values** in the built-in rules are replaced as one
|
|
93
|
+
stand-in over all the characters either of them covers. Before, the longer
|
|
94
|
+
one was kept and the rest of the shorter one was sent as written (for
|
|
95
|
+
example the tail of a social security number that followed an IBAN).
|
|
96
|
+
- `coverage` values are now `full`, `rules_and_names` and `rules_only`. The
|
|
97
|
+
engine without its name model reports `rules_and_names` (was `rules_only`);
|
|
98
|
+
the engine with it reports `full` (was `engine`).
|
|
99
|
+
- The reduced-coverage notice on standard error is one line
|
|
100
|
+
(`cloakapi: warning reduced_coverage (engine_missing): ...`), once per process
|
|
101
|
+
per reason. Before, it was a three-line banner.
|
|
102
|
+
- Text given as a binary-tagged or non-UTF-8 string is read as, or converted
|
|
103
|
+
to, UTF-8 before detection.
|
|
104
|
+
|
|
105
|
+
### Added
|
|
106
|
+
|
|
107
|
+
- Review callback: `CloakAPI::Client.new(key, review: ->(text, info) { ... })`
|
|
108
|
+
and `create(model:, messages:, ...)` in one call; also `review:` per call.
|
|
109
|
+
- `prepared.text`, `prepared.coverage`, `prepared.warnings`, `prepared.state`,
|
|
110
|
+
`prepared.info`; `client.approve(prepared)`; `send_approved(approved)`.
|
|
111
|
+
- `reply.coverage` and `reply.warnings` on the reply of `create`.
|
|
112
|
+
- `CloakAPI::SendWarning` (`code`, `reason`, `message`), `CloakAPI::ReviewInfo`,
|
|
113
|
+
`CloakAPI::Coverage`, `CloakAPI::ReviewRequiredError` (an `ArgumentError`).
|
|
114
|
+
- `CloakAPI::Engine.status` (`used?`, `reason`, `message`, `sha256`, `source`).
|
|
115
|
+
- `strict_coverage: true` as the name of the explicit strict option
|
|
116
|
+
(`allow_reduced_coverage: false` keeps working).
|
|
117
|
+
- `examples/hello.rb` and `examples/fake_gateway.rb`.
|
|
118
|
+
- Diagnostics for a failed engine load name the system's glibc version, or musl.
|
|
119
|
+
|
|
120
|
+
- **Inline media no longer stops a request.** An image, a `data:` URL or a
|
|
121
|
+
file reference in a message is sent as provided with the warning
|
|
122
|
+
`unchecked_content` / `media_not_checked` (before: `ArgumentError`, "requires
|
|
123
|
+
local file review"). It is not scanned or rewritten.
|
|
124
|
+
- A JSON number of 6 to 16 digits that looks like personal data stays a number
|
|
125
|
+
and the request carries the sentence "A number looks like personal data...".
|
|
126
|
+
|
|
127
|
+
### Fixed
|
|
128
|
+
|
|
129
|
+
- A stand-in directly followed by a full stop (or by `@`, `+`, `-`) was left out
|
|
130
|
+
of the request's restore map, so the reply came back with the stand-in in
|
|
131
|
+
place of the original value. Every stand-in that goes out is restored.
|
|
132
|
+
- On Ruby 4.0 (json 2.15 and newer) a receipt with the same member twice was
|
|
133
|
+
accepted by `Receipts.verify_receipt`; it is refused again.
|
|
134
|
+
- `require "cloakapi"` no longer needs the `base64` gem (not part of Ruby's
|
|
135
|
+
default gems since 3.4) or the `cgi` library (not since 3.5). Under Bundler
|
|
136
|
+
on those versions the require failed.
|
|
137
|
+
- The SDK loads without `fiddle`; it then works on its built-in rules.
|
|
138
|
+
- A file tokenised while another thread tokenised text on the same client could
|
|
139
|
+
overwrite that thread's update of the conversation memory.
|
|
140
|
+
- An empty detected span at the start of a longer one could leave part of the
|
|
141
|
+
longer value in the text.
|
|
142
|
+
|
|
143
|
+
### Kept
|
|
144
|
+
|
|
145
|
+
- `prepare` / `approve` / `create(approved)` / `create_stream(approved)`,
|
|
146
|
+
`preview`, `allow_reduced_coverage:`, `last_detection_status`,
|
|
147
|
+
`validate_engine_identity!` (now never raises for the engine), and the
|
|
148
|
+
`unsafe_raw_*` methods work as before.
|
|
149
|
+
|
|
150
|
+
### Packaging
|
|
151
|
+
|
|
152
|
+
- No engine file inside the default gem (1.3.0 carried a withdrawn 1.6.0
|
|
153
|
+
build). A platform build may carry one of the two engine builds the release
|
|
154
|
+
set names; the gemspec refuses any other file.
|
|
155
|
+
- `webrick` is a development dependency (the test suite needs it; it has not
|
|
156
|
+
come with Ruby since 3.0).
|
|
157
|
+
|
|
158
|
+
## 1.3.1 and earlier
|
|
159
|
+
|
|
160
|
+
Not recorded in this file.
|
data/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright 2024-2026 Klokk Nettablering
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
data/NOTICE
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
CloakAPI SDK for Ruby
|
|
2
|
+
Copyright 2024-2026 Klokk Nettablering (org. no. 821 466 962, Norway)
|
|
3
|
+
|
|
4
|
+
This product is licensed under the Apache License, Version 2.0 (see LICENSE).
|
|
5
|
+
|
|
6
|
+
This package includes the CloakAPI rule set under the same license.
|
|
7
|
+
Where a build also ships a compiled engine, that binary is under the
|
|
8
|
+
same license. The engine's source code is not distributed with this package.
|
|
9
|
+
|
|
10
|
+
"CloakAPI" and "Verified by CloakAPI" are trademarks of Klokk Nettablering.
|
|
11
|
+
The Apache License does not grant permission to use them (section 6);
|
|
12
|
+
see TRADEMARKS.md.
|
|
13
|
+
|
|
14
|
+
This product includes third-party software and data. Their notices and
|
|
15
|
+
license texts are in THIRD-PARTY-NOTICES.md and the licenses/ directory.
|
|
16
|
+
Place names are derived from GeoNames (https://www.geonames.org/), licensed
|
|
17
|
+
under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/); modified by
|
|
18
|
+
filtering and compaction.
|