@flop-labs/cli 0.0.0-stage → 0.4.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 +233 -0
- package/LICENSE +238 -0
- package/README.md +501 -2
- package/dist/cli.js +13237 -0
- package/package.json +55 -3
package/CHANGELOG.md
ADDED
|
@@ -0,0 +1,233 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
All notable changes to `@flop-labs/cli` are documented here.
|
|
4
|
+
|
|
5
|
+
The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/)
|
|
6
|
+
and this package follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
|
+
|
|
8
|
+
## [Unreleased]
|
|
9
|
+
|
|
10
|
+
## [0.4.1] - 2026-11-08
|
|
11
|
+
|
|
12
|
+
### Added
|
|
13
|
+
|
|
14
|
+
- Gateway renewal follows the same operator-owned static-to-public handoffs as the gateway,
|
|
15
|
+
retaining admission expiry, identity checks and static budget ceilings.
|
|
16
|
+
|
|
17
|
+
- Gateway renewal consumes optional dynamic admissions, verifies their pinned identity and
|
|
18
|
+
uses channel-signed paid conformance probes without extending admission or location evidence.
|
|
19
|
+
|
|
20
|
+
### Fixed
|
|
21
|
+
|
|
22
|
+
- Report session failures as structured nonzero errors with channel recovery guidance.
|
|
23
|
+
- Route package bug reports to the public network issue forms.
|
|
24
|
+
|
|
25
|
+
- Require a fresh dynamic admission before expiry-bound renewal probes, even when a static
|
|
26
|
+
route shadows that slot; retain operator handoff withdrawal checks.
|
|
27
|
+
|
|
28
|
+
- Bound unreachable RPC connections and release wallet-creation connections after errors.
|
|
29
|
+
- Report balance totals including reserves and expose frozen funds; retain the live validator
|
|
30
|
+
minimum in JSON, human and agent output, including an explicit offline state.
|
|
31
|
+
- Resolve exact model names before hash queries and carry the resolved hash into chat.
|
|
32
|
+
- Preflight caller-supplied HTLC appraisal commitments against finalized governed state;
|
|
33
|
+
missing profiles remain unavailable. Forward the appraisal tuple through chat's agent
|
|
34
|
+
inference handoff. Surface faucet readiness and server retry guidance.
|
|
35
|
+
|
|
36
|
+
## [0.4.0] - 2026-10-28
|
|
37
|
+
|
|
38
|
+
### Added
|
|
39
|
+
|
|
40
|
+
- `flop model preflight --source <hf-id> [--revision]` prints a checkpoint's `content_root`,
|
|
41
|
+
packed image size, DA chunk count and stored tensor elements from hub metadata. It downloads
|
|
42
|
+
no weights.
|
|
43
|
+
- `flop model onboard --download` keeps the download-and-pack path for a Hugging Face source.
|
|
44
|
+
It uploads the DA backup as the packed image plus its file table, and the DA mirror names the
|
|
45
|
+
table.
|
|
46
|
+
- `gateway renew` can verify and append a settled owner tools-qualification receipt without another paid probe. Receipt-only publication preserves unrelated evidence, original proof-bound timestamps and declared windows, refuses conflicting updates and retains the existing direct-probe mode.
|
|
47
|
+
- `flop model onboard` accepts FP8 checkpoints declared as compressed-tensors, `fbgemm_fp8`, ModelOpt in `config.json`, or per-tensor `quant_method: fp8`, and registers them with the `fp8` catalog label over their BF16 activation dtype. Other schemes in those formats (INT8, NVFP4, MXFP8) are still refused before registration, naming the field.
|
|
48
|
+
- Released on public npm as `@flop-labs/cli` through the `cli-v*` tag lane, licensed under
|
|
49
|
+
`MIT OR Apache-2.0` at your option (`LICENSE` carries both texts), with repository metadata.
|
|
50
|
+
Run it without a global install:
|
|
51
|
+
`npx --yes --package @flop-labs/cli@<version> flop --help`.
|
|
52
|
+
- Public launcher 0.4.0 includes a pinned native `flop-public` Hermes plugin, wallet authentication and shared-cache validation; stable Hermes 0.22.2 is the supported baseline. Enrollment and paid inference still require separately available service capacity.
|
|
53
|
+
|
|
54
|
+
- Model onboarding accepts an independent registrar keystore for direct registration pins and explicit `--approve`; approval and approval recovery recheck finalized admission evidence, while local chains retain legacy sudo compatibility. Output distinguishes registration from approval.
|
|
55
|
+
|
|
56
|
+
- A standalone public Hermes launcher with checksum-verified installation, free model discovery, scoped wallet enrollment, an isolated bounded profile and external acceptance tooling. The full CLI remains version 0.3.0; the hosted-only archive is version 0.3.4.
|
|
57
|
+
|
|
58
|
+
- `flop gateway renew` re-observes each allowlisted miner and writes the gateway evidence file.
|
|
59
|
+
It checks the GPU.ai instance named in `deployment.source`, authenticated `/session/info`, and
|
|
60
|
+
the finalized chain, and re-runs `tools` conformance as a paid compute-channel turn from a
|
|
61
|
+
dedicated signer. Each renewal keeps its declared window length. Anything it cannot observe is
|
|
62
|
+
left to lapse. `sdk/cli/Dockerfile` builds the `cli` image the core box runs it from hourly.
|
|
63
|
+
- Add a resumable private `model audit` caller and historical-completion revalidation in `model onboard --paid-admission`; current pre-escrow readiness remains blocked.
|
|
64
|
+
|
|
65
|
+
- `flop model onboard` retains a private workspace across reruns, checks remote config before downloading weights, pins `--revision`, revalidates cached bytes and recovers exact signed transactions at finality. `--state-dir` selects the workspace; registration remains distinct from paid admission.
|
|
66
|
+
- `--paid-admission --session-endpoint` rechecks authenticated serving and finalized calibration prerequisites; it fails before escrow while the independent-audit completion adapter is unavailable.
|
|
67
|
+
|
|
68
|
+
- `flop model onboard --soft` registers non-attested models with no TEE platform
|
|
69
|
+
claim and rejects conflicting attestation metadata on a rerun.
|
|
70
|
+
- `flop gateway allowlist` emits both gateway environment values after checking
|
|
71
|
+
authenticated miner identity, model/decode-policy registry state, renewable
|
|
72
|
+
calibration, and operator/provider evidence on the selected network.
|
|
73
|
+
- `flop model onboard` performs reproducible packing, capture/coherence admission,
|
|
74
|
+
DA publication, and idempotent per-precision registry setup in one command.
|
|
75
|
+
- `flop keys claude-profile` creates a private Claude Code settings profile whose helper refreshes scope-locked ephemeral gateway tokens.
|
|
76
|
+
- `flop --network devnet agent credential` enrolls at the public gateway with a wallet
|
|
77
|
+
signature by default: it creates a local devnet sr25519 account, funds it from the
|
|
78
|
+
faucet when below 1 FLOP, and signs the gateway's challenge. `--tailnet` keeps the
|
|
79
|
+
private `gateway.ts.flop.network:3201` lane, which `hermes desktop` uses only when
|
|
80
|
+
`--gateway` names the tailnet gateway.
|
|
81
|
+
- Operator release checks cache the published manifest for 24 hours, warn on older builds,
|
|
82
|
+
and refuse state changes below the supported minimum. `--offline` skips the check;
|
|
83
|
+
`--version` reports the stamped image version when present.
|
|
84
|
+
- `flop session run` sends verified inference to a named miner with keystore signing or a
|
|
85
|
+
faucet-funded devnet test wallet, and reports its channel and settlement transaction.
|
|
86
|
+
- `flop miner declare-gpu` publishes a registered miner's self-reported GPU inventory as a signed
|
|
87
|
+
`flop.gpu-inventory.v1` remark, read from `nvidia-smi` output (`--nvidia-smi`) or detected on the
|
|
88
|
+
host (`--detect`), and `--retract` withdraws it. It is display-only; the format and indexing rules are in
|
|
89
|
+
`docs/design/gpu-inventory-remark.md`.
|
|
90
|
+
- `flop gateway renew` renews tailnet-hosted miners (`operator-observed:tailscale/<host> egress
|
|
91
|
+
<ipv4> AS<n>`) while the host's tailscaled sees the node online, tagged `tag:miner`, at that
|
|
92
|
+
egress (`--tailscale-socket`, default `/var/run/tailscale/tailscaled.sock`). GPU.ai sources are
|
|
93
|
+
unchanged.
|
|
94
|
+
- `flop gateway renew` checks, before each paid `tools` probe, that the probe signer holds at
|
|
95
|
+
least one `--probe-escrow` free at the finalized head. When it does not, the run stops probing
|
|
96
|
+
and prints `gateway renew: PROBE SIGNER UNDERFUNDED: …` on stderr. It still writes every
|
|
97
|
+
deployment it renewed, and exits 1. Each withdrawn feature's reason reads `probe not run: …`.
|
|
98
|
+
|
|
99
|
+
### Changed
|
|
100
|
+
|
|
101
|
+
- `flop model onboard` registers `model_hash` as the checkpoint's `content_root` (`content-v1`,
|
|
102
|
+
D-0535) instead of its dm-verity root. A Hugging Face source registers from the hub's published
|
|
103
|
+
sha256 table without downloading weights. That metadata-only run uploads no DA backup and refuses
|
|
104
|
+
`--approve`. Approval now also requires the DA mirror to name a Leased file table that hashes to
|
|
105
|
+
`model_hash`. A workspace that prepared a `verity-v1` identity refuses to register the content
|
|
106
|
+
root as well.
|
|
107
|
+
- `flop model upload` and `flop model fetch` accept a registered root under either scheme.
|
|
108
|
+
- **Breaking (packaging):** `dist/` holds one bundled `dist/cli.js`. It inlines the
|
|
109
|
+
unpublished `@flop-labs/agent-sdk` and `@flop-labs/gateway-core`; every other import is a
|
|
110
|
+
declared dependency. The other files under `dist/` are gone. `node sdk/cli/dist/cli.js` and
|
|
111
|
+
the `cli` image entrypoint are unchanged.
|
|
112
|
+
- `flop --version` reports the package version; it printed a hard-coded 0.3.0.
|
|
113
|
+
- `flop --network devnet agent init` / `agent doctor` default to the public
|
|
114
|
+
`https://mcp.flop.network/mcp` instead of the tailnet-only `mcp.ts.flop.network`.
|
|
115
|
+
- Hosted Hermes launch and Claude profile creation use the shared HTTP client
|
|
116
|
+
to validate public model catalogs. Claude profiles still require the exact
|
|
117
|
+
model identity before creating a credential helper.
|
|
118
|
+
- The proxy's nonstreaming chat response is checked against the generated API
|
|
119
|
+
contract. Its catalog fetch preserves legacy array and minimal-model shapes;
|
|
120
|
+
those are outside the shared client's canonical catalog contract.
|
|
121
|
+
- **Breaking:** the minimum supported Node version is now 22. `@flop-labs/gateway-core`,
|
|
122
|
+
which `flop gateway allowlist` depends on, requires Node >= 22, so the previous
|
|
123
|
+
`>=18` range let the CLI install onto runtimes its dependencies do not support.
|
|
124
|
+
- `flop keys claude-profile` requires an exact model slug and mints its identity
|
|
125
|
+
from the gateway's live public catalog instead of baked-in Claude-to-Llama aliases.
|
|
126
|
+
- Miner calibration status now reports the active benchmark-burst cap; worker
|
|
127
|
+
supervision replaces the manual calibration-start command.
|
|
128
|
+
- Miner onboarding accepts counted, repeatable GPU inventory hints; status can
|
|
129
|
+
compare them with attested inventory, and `miner skus` lists live governed
|
|
130
|
+
ceilings.
|
|
131
|
+
- `flop model upload` and `flop model onboard` stream the packed image to DA from
|
|
132
|
+
disk: `da-validator commit` hashes it into its commitment one 64 MiB chunk at a
|
|
133
|
+
time, the blob is registered, and `da-validator submit` pushes it chunk by chunk.
|
|
134
|
+
Rerunning the same command after an interruption resumes the push, and the
|
|
135
|
+
result reports per-chunk custody. An image larger than one chunk commits to a
|
|
136
|
+
Merkle root over its chunks, so these commands need a `da-validator` with
|
|
137
|
+
chunked DA. `model upload --path` now packs with modelpack instead of in memory.
|
|
138
|
+
- `flop hermes` discovers supported models, including unloaded ones, and allows bounded cold
|
|
139
|
+
loading: requests carry a one-hour `max_wait_ms`, Hermes request and stale timeouts are
|
|
140
|
+
3,900 seconds, an agent run may take three hours, and readiness, discovery and enrollment
|
|
141
|
+
reads allow 30 seconds. Spending, output and turn caps are unchanged.
|
|
142
|
+
|
|
143
|
+
### Removed
|
|
144
|
+
|
|
145
|
+
- Removed the legacy manual miner calibration-start path.
|
|
146
|
+
|
|
147
|
+
### Fixed
|
|
148
|
+
|
|
149
|
+
- `flop model onboard` refuses a block-FP8 `quantization_config` (with `weight_block_size`) outside the reviewed Qwen layout before registration, naming the field. It used to register any `quant_method: fp8` checkpoint as plain `fp8`.
|
|
150
|
+
- Public Hermes plugin installation creates its private default cache parent before Hermes initializes a nested profile during version probing.
|
|
151
|
+
|
|
152
|
+
- `model upload` and `model onboard` pass the signer's sr25519 key to `da-validator submit` through `DA_PUBLISHER_KEY`, so each pushed DA shard is signed by the account that registered the blob; DA workers now refuse unsigned shard uploads. A signer without an sr25519 key is refused before it registers a new blob; it can still reuse a blob that is already registered, whose placed custody is then verified without pushing.
|
|
153
|
+
|
|
154
|
+
- Public Hermes profiles honor the gateway’s disabled-reasoning route without sending unsupported reasoning controls and keep terminal tools directly exposed without tool discovery.
|
|
155
|
+
|
|
156
|
+
- Hybrid onboarding counts all pinned safetensors parameters before immutable registration, binds the census to packed source bytes, and rejects conflicting historical or pending counts.
|
|
157
|
+
- Model onboarding resumes after a competing finalized transaction consumes its pending nonce, without rebroadcasting stale bytes or repeating already-finalized registration. Unknown history, pool rejection and finality timeout retain the original signed transaction for reconciliation.
|
|
158
|
+
|
|
159
|
+
- Validator registration and status use the SDK's effective minimum, including
|
|
160
|
+
the value-coupled floor; command help describes the exact minimum bond.
|
|
161
|
+
- `flop validator status <ADDRESS>` and `flop miner status <ADDRESS>` query public
|
|
162
|
+
chain state without requiring or loading an operator signer.
|
|
163
|
+
- `flop model upload` registers the DA blob before pushing its shards. It used to
|
|
164
|
+
push first, and every validator dropped the shards of the unregistered blob.
|
|
165
|
+
- `flop gateway allowlist` reads `modelRegistry.measuredRoots` (the pallet's storage name); it
|
|
166
|
+
queried `measuredRoot` and refused every chain with "model-registry gateway queries are
|
|
167
|
+
unavailable on this runtime".
|
|
168
|
+
- `flop miner register` no longer fails with "Cannot read properties of undefined", and
|
|
169
|
+
`flop miner status` no longer reports a registered miner as unregistered (SDK staking
|
|
170
|
+
clients now use polkadot-js's camelCase pallet names).
|
|
171
|
+
- `--network devnet` without `--rpc` now connects to the public `wss://rpc.devnet.flop.network`
|
|
172
|
+
(funds through `https://faucet.flop.network` and targets the gateway at
|
|
173
|
+
`https://api.flop.network`) instead of the retired `ws://node.ts.flop.network:9944`
|
|
174
|
+
and the tailnet-only `http://gateway.ts.flop.network`.
|
|
175
|
+
- File-destination options no longer overload the global `--output` mode: `keys
|
|
176
|
+
generate`, `keys import`, `keys export`, and `tx build` now write to `--out
|
|
177
|
+
<path>`, so `--output agent`/`json` machine output works alongside a written
|
|
178
|
+
artifact.
|
|
179
|
+
- An overridden `--rpc` that matches no known FLOP network now fails closed
|
|
180
|
+
instead of defaulting to `local` (and the `//Alice` dev key); pass `--network`
|
|
181
|
+
to select a profile for a custom endpoint.
|
|
182
|
+
- Miner doctor/status authenticate session-info with the host-local
|
|
183
|
+
`SESSION_AUTH_TOKEN` and report image/controller capability and readiness.
|
|
184
|
+
An authentication failure or a cold controller does not report ready.
|
|
185
|
+
- `flop model onboard` reads a checkpoint's ModelOpt `hf_quant_config.json` at preflight and after
|
|
186
|
+
download. FP8 is labeled `fp8`; other declared algorithms are refused before registration instead
|
|
187
|
+
of being registered as unquantized BF16.
|
|
188
|
+
- `flop session run` uses the SDK's 256-token completion budget and accepts `--max-tokens`.
|
|
189
|
+
Invalid limits fail before connecting or funding; JSON output includes `finish_reason`
|
|
190
|
+
and `completion_tokens` so a length-limited response is explicit.
|
|
191
|
+
|
|
192
|
+
## [0.3.0] - 2026-07-24
|
|
193
|
+
|
|
194
|
+
### Added
|
|
195
|
+
|
|
196
|
+
- Canonical network profiles, network status, and genesis-checked faucet requests.
|
|
197
|
+
- Model list/get, verified multi-source fetch, and source-to-DA upload.
|
|
198
|
+
- Session enumeration, session-backed proxy/chat, and persistent chat history.
|
|
199
|
+
- Encrypted keystore generate/import/export, multisig, hardware status, and air-gapped transaction envelopes.
|
|
200
|
+
|
|
201
|
+
### Changed
|
|
202
|
+
|
|
203
|
+
- Key names are metadata; generated key material is always random.
|
|
204
|
+
- Unknown model IDs are rejected instead of echoed.
|
|
205
|
+
- Devnet faucet routing and the live anonymous 25 FLOP default are canonical.
|
|
206
|
+
|
|
207
|
+
## [0.2.0] - 2026-07-24
|
|
208
|
+
|
|
209
|
+
### Added
|
|
210
|
+
|
|
211
|
+
- Unified `agent`, `miner`, and `validator` command groups.
|
|
212
|
+
- Compact `--output agent` results with stable structured errors and next
|
|
213
|
+
actions.
|
|
214
|
+
- Hermes desktop launch under `flop agent hermes desktop`, while preserving the
|
|
215
|
+
existing top-level command.
|
|
216
|
+
- Read-only onboarding plans and role-specific `doctor` checks.
|
|
217
|
+
- Miner registration, calibration start, and combined chain/session status.
|
|
218
|
+
- Validator registration, commission, recovery, exit, and eligibility status.
|
|
219
|
+
- Network-free tests for role plans, safety labels, command registration, and
|
|
220
|
+
deeply nested global CLI options.
|
|
221
|
+
|
|
222
|
+
### Changed
|
|
223
|
+
|
|
224
|
+
- Existing agent launch, proxy, key, wallet, and session commands are available
|
|
225
|
+
under `flop agent` while their top-level compatibility paths remain.
|
|
226
|
+
- CLI global `--rpc` and `--signer` lookup now works at any command nesting depth.
|
|
227
|
+
- Agent-mode onboarding plans omit explanatory prose, and doctor reports return
|
|
228
|
+
only blockers and warnings.
|
|
229
|
+
|
|
230
|
+
[Unreleased]: https://github.com/flop-labs/flop-core/compare/cli-v0.4.0...HEAD
|
|
231
|
+
[0.4.0]: https://github.com/flop-labs/flop-core/compare/v0.3.0...cli-v0.4.0
|
|
232
|
+
[0.3.0]: https://github.com/flop-labs/flop-core/compare/services-v0.0.0-devnet.20260724.2...v0.3.0
|
|
233
|
+
[0.2.0]: https://github.com/flop-labs/flop-core/compare/services-v0.0.0-devnet.20260724.2...HEAD
|
package/LICENSE
ADDED
|
@@ -0,0 +1,238 @@
|
|
|
1
|
+
Copyright (c) 2025-2026 The FLOP Network Contributors
|
|
2
|
+
|
|
3
|
+
This package is licensed under either of
|
|
4
|
+
|
|
5
|
+
* the MIT license (first text below), or
|
|
6
|
+
* the Apache License, Version 2.0 (second text below)
|
|
7
|
+
|
|
8
|
+
at your option.
|
|
9
|
+
|
|
10
|
+
SPDX-License-Identifier: MIT OR Apache-2.0
|
|
11
|
+
|
|
12
|
+
================================================================================
|
|
13
|
+
|
|
14
|
+
MIT License
|
|
15
|
+
|
|
16
|
+
Copyright (c) 2025-2026 The FLOP Network Contributors
|
|
17
|
+
|
|
18
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
19
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
20
|
+
in the Software without restriction, including without limitation the rights
|
|
21
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
22
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
23
|
+
furnished to do so, subject to the following conditions:
|
|
24
|
+
|
|
25
|
+
The above copyright notice and this permission notice shall be included in all
|
|
26
|
+
copies or substantial portions of the Software.
|
|
27
|
+
|
|
28
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
29
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
30
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
31
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
32
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
33
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
34
|
+
SOFTWARE.
|
|
35
|
+
|
|
36
|
+
================================================================================
|
|
37
|
+
|
|
38
|
+
Apache License
|
|
39
|
+
Version 2.0, January 2004
|
|
40
|
+
http://www.apache.org/licenses/
|
|
41
|
+
|
|
42
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
43
|
+
|
|
44
|
+
1. Definitions.
|
|
45
|
+
|
|
46
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
47
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
48
|
+
|
|
49
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
50
|
+
the copyright owner that is granting the License.
|
|
51
|
+
|
|
52
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
53
|
+
other entities that control, are controlled by, or are under common
|
|
54
|
+
control with that entity. For the purposes of this definition,
|
|
55
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
56
|
+
direction or management of such entity, whether by contract or
|
|
57
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
58
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
59
|
+
|
|
60
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
61
|
+
exercising permissions granted by this License.
|
|
62
|
+
|
|
63
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
64
|
+
including but not limited to software source code, documentation
|
|
65
|
+
source, and configuration files.
|
|
66
|
+
|
|
67
|
+
"Object" form shall mean any form resulting from mechanical
|
|
68
|
+
transformation or translation of a Source form, including but
|
|
69
|
+
not limited to compiled object code, generated documentation,
|
|
70
|
+
and conversions to other media types.
|
|
71
|
+
|
|
72
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
73
|
+
Object form, made available under the License, as indicated by a
|
|
74
|
+
copyright notice that is included in or attached to the work
|
|
75
|
+
(an example is provided in the Appendix below).
|
|
76
|
+
|
|
77
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
78
|
+
form, that is based on (or derived from) the Work and for which the
|
|
79
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
80
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
81
|
+
of this License, Derivative Works shall not include works that remain
|
|
82
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
83
|
+
the Work and Derivative Works thereof.
|
|
84
|
+
|
|
85
|
+
"Contribution" shall mean any work of authorship, including
|
|
86
|
+
the original version of the Work and any modifications or additions
|
|
87
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
88
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
89
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
90
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
91
|
+
means any form of electronic, verbal, or written communication sent
|
|
92
|
+
to the Licensor or its representatives, including but not limited to
|
|
93
|
+
communication on electronic mailing lists, source code control systems,
|
|
94
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
95
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
96
|
+
excluding communication that is conspicuously marked or otherwise
|
|
97
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
98
|
+
|
|
99
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
100
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
101
|
+
subsequently incorporated within the Work.
|
|
102
|
+
|
|
103
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
104
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
105
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
106
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
107
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
108
|
+
Work and such Derivative Works in Source or Object form.
|
|
109
|
+
|
|
110
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
111
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
112
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
113
|
+
(except as stated in this section) patent license to make, have made,
|
|
114
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
115
|
+
where such license applies only to those patent claims licensable
|
|
116
|
+
by such Contributor that are necessarily infringed by their
|
|
117
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
118
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
119
|
+
institute patent litigation against any entity (including a
|
|
120
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
121
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
122
|
+
or contributory patent infringement, then any patent licenses
|
|
123
|
+
granted to You under this License for that Work shall terminate
|
|
124
|
+
as of the date such litigation is filed.
|
|
125
|
+
|
|
126
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
127
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
128
|
+
modifications, and in Source or Object form, provided that You
|
|
129
|
+
meet the following conditions:
|
|
130
|
+
|
|
131
|
+
(a) You must give any other recipients of the Work or
|
|
132
|
+
Derivative Works a copy of this License; and
|
|
133
|
+
|
|
134
|
+
(b) You must cause any modified files to carry prominent notices
|
|
135
|
+
stating that You changed the files; and
|
|
136
|
+
|
|
137
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
138
|
+
that You distribute, all copyright, patent, trademark, and
|
|
139
|
+
attribution notices from the Source form of the Work,
|
|
140
|
+
excluding those notices that do not pertain to any part of
|
|
141
|
+
the Derivative Works; and
|
|
142
|
+
|
|
143
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
144
|
+
distribution, then any Derivative Works that You distribute must
|
|
145
|
+
include a readable copy of the attribution notices contained
|
|
146
|
+
within such NOTICE file, excluding those notices that do not
|
|
147
|
+
pertain to any part of the Derivative Works, in at least one
|
|
148
|
+
of the following places: within a NOTICE text file distributed
|
|
149
|
+
as part of the Derivative Works; within the Source form or
|
|
150
|
+
documentation, if provided along with the Derivative Works; or,
|
|
151
|
+
within a display generated by the Derivative Works, if and
|
|
152
|
+
wherever such third-party notices normally appear. The contents
|
|
153
|
+
of the NOTICE file are for informational purposes only and
|
|
154
|
+
do not modify the License. You may add Your own attribution
|
|
155
|
+
notices within Derivative Works that You distribute, alongside
|
|
156
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
157
|
+
that such additional attribution notices cannot be construed
|
|
158
|
+
as modifying the License.
|
|
159
|
+
|
|
160
|
+
You may add Your own copyright statement to Your modifications and
|
|
161
|
+
may provide additional or different license terms and conditions
|
|
162
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
163
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
164
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
165
|
+
the conditions stated in this License.
|
|
166
|
+
|
|
167
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
168
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
169
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
170
|
+
this License, without any additional terms or conditions.
|
|
171
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
172
|
+
the terms of any separate license agreement you may have executed
|
|
173
|
+
with Licensor regarding such Contributions.
|
|
174
|
+
|
|
175
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
176
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
177
|
+
except as required for reasonable and customary use in describing the
|
|
178
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
179
|
+
|
|
180
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
181
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
182
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
183
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
184
|
+
implied, including, without limitation, any warranties or conditions
|
|
185
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
186
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
187
|
+
appropriateness of using or redistributing the Work and assume any
|
|
188
|
+
risks associated with Your exercise of permissions under this License.
|
|
189
|
+
|
|
190
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
191
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
192
|
+
unless required by applicable law (such as deliberate and grossly
|
|
193
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
194
|
+
liable to You for damages, including any direct, indirect, special,
|
|
195
|
+
incidental, or consequential damages of any character arising as a
|
|
196
|
+
result of this License or out of the use or inability to use the
|
|
197
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
198
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
199
|
+
other commercial damages or losses), even if such Contributor
|
|
200
|
+
has been advised of the possibility of such damages.
|
|
201
|
+
|
|
202
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
203
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
204
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
205
|
+
or other liability obligations and/or rights consistent with this
|
|
206
|
+
License. However, in accepting such obligations, You may act only
|
|
207
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
208
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
209
|
+
defend, and hold each Contributor harmless for any liability
|
|
210
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
211
|
+
of your accepting any such warranty or additional liability.
|
|
212
|
+
|
|
213
|
+
END OF TERMS AND CONDITIONS
|
|
214
|
+
|
|
215
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
216
|
+
|
|
217
|
+
To apply the Apache License to your work, attach the following
|
|
218
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
219
|
+
replaced with your own identifying information. (Don't include
|
|
220
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
221
|
+
comment syntax for the file format. We also recommend that a
|
|
222
|
+
file or class name and description of purpose be included on the
|
|
223
|
+
same "printed page" as the copyright notice for easier
|
|
224
|
+
identification within third-party archives.
|
|
225
|
+
|
|
226
|
+
Copyright [yyyy] [name of copyright owner]
|
|
227
|
+
|
|
228
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
229
|
+
you may not use this file except in compliance with the License.
|
|
230
|
+
You may obtain a copy of the License at
|
|
231
|
+
|
|
232
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
233
|
+
|
|
234
|
+
Unless required by applicable law or agreed to in writing, software
|
|
235
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
236
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
237
|
+
See the License for the specific language governing permissions and
|
|
238
|
+
limitations under the License.
|