meld-cli 0.65.1__py3-none-macosx_11_0_arm64.whl
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.
|
Binary file
|
|
@@ -0,0 +1,297 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: meld-cli
|
|
3
|
+
Version: 0.65.1
|
|
4
|
+
Summary: Static WebAssembly component fusion (the `meld` command-line tool)
|
|
5
|
+
Keywords: webassembly,component-model,fusion,cli
|
|
6
|
+
Author: PulseEngine
|
|
7
|
+
License-Expression: Apache-2.0
|
|
8
|
+
License-File: LICENSE
|
|
9
|
+
Classifier: Environment :: Console
|
|
10
|
+
Classifier: Intended Audience :: Developers
|
|
11
|
+
Classifier: Programming Language :: Rust
|
|
12
|
+
Classifier: Topic :: Software Development :: Compilers
|
|
13
|
+
Project-URL: Homepage, https://github.com/pulseengine/meld
|
|
14
|
+
Project-URL: Repository, https://github.com/pulseengine/meld
|
|
15
|
+
Project-URL: Changelog, https://github.com/pulseengine/meld/blob/main/CHANGELOG.md
|
|
16
|
+
Project-URL: Issues, https://github.com/pulseengine/meld/issues
|
|
17
|
+
Requires-Python: >=3.8
|
|
18
|
+
Description-Content-Type: text/markdown
|
|
19
|
+
|
|
20
|
+
<div align="center">
|
|
21
|
+
|
|
22
|
+
# Meld
|
|
23
|
+
|
|
24
|
+
<sup>Static WebAssembly component fusion</sup>
|
|
25
|
+
|
|
26
|
+
|
|
27
|
+
|
|
28
|
+
[](https://github.com/pulseengine/meld/actions/workflows/ci.yml)
|
|
29
|
+
[](https://github.com/pulseengine/meld/actions/workflows/bench.yml)
|
|
30
|
+
[](https://codecov.io/gh/pulseengine/meld)
|
|
31
|
+
|
|
32
|
+
|
|
33
|
+
|
|
34
|
+
[-2962FF?style=flat-square&logoColor=white&labelColor=1a1b27)](#formal-verification)
|
|
35
|
+
|
|
36
|
+
|
|
37
|
+
|
|
38
|
+
|
|
39
|
+
<h6>
|
|
40
|
+
<a href="https://github.com/pulseengine/meld">Meld</a>
|
|
41
|
+
·
|
|
42
|
+
<a href="https://github.com/pulseengine/loom">Loom</a>
|
|
43
|
+
·
|
|
44
|
+
<a href="https://github.com/pulseengine/synth">Synth</a>
|
|
45
|
+
·
|
|
46
|
+
<a href="https://github.com/pulseengine/kiln">Kiln</a>
|
|
47
|
+
·
|
|
48
|
+
<a href="https://github.com/pulseengine/sigil">Sigil</a>
|
|
49
|
+
</h6>
|
|
50
|
+
|
|
51
|
+
</div>
|
|
52
|
+
|
|
53
|
+
|
|
54
|
+
|
|
55
|
+
Meld fuses. Loom weaves. Synth transpiles. Kiln fires. Sigil seals.
|
|
56
|
+
|
|
57
|
+
Meld statically fuses multiple WebAssembly components into a single core module, eliminating the need for runtime linking. Import resolution, index-space merging, and canonical ABI adapter generation happen at build time. The core transformations — resolution, index-space merging, and adapter generation — carry mechanized Rocq proofs, plus local Kani bounded-model-checking harnesses on the Canonical-ABI layout invariants; see [Formal Verification](#formal-verification) for the per-stage coverage (some stages are specified but not yet proved, and the Kani harnesses are run locally, not gated in CI).
|
|
58
|
+
|
|
59
|
+
Unlike composition tools that produce linked-but-separate component graphs, Meld produces a single monolithic module suitable for whole-program optimization by Loom and native transpilation by Synth.
|
|
60
|
+
|
|
61
|
+
## Quick Start
|
|
62
|
+
|
|
63
|
+
### Prebuilt binaries
|
|
64
|
+
|
|
65
|
+
Every release ships archives for six targets. On Linux, pick by what the
|
|
66
|
+
machine has rather than by architecture alone:
|
|
67
|
+
|
|
68
|
+
| | use |
|
|
69
|
+
|---|---|
|
|
70
|
+
| glibc 2.34 or newer (Ubuntu 22.04+, Debian 12+, Fedora) | `*-unknown-linux-gnu` |
|
|
71
|
+
| **anything older, or no glibc at all** — Alpine, distroless-static, RHEL 8, Ubuntu 20.04 | `*-unknown-linux-musl` |
|
|
72
|
+
| macOS | `*-apple-darwin` |
|
|
73
|
+
|
|
74
|
+
The musl archives are statically linked: no dynamic loader, no glibc symbol
|
|
75
|
+
versions, nothing to install alongside them. If you are not sure which your
|
|
76
|
+
target has, the musl one runs in both places.
|
|
77
|
+
|
|
78
|
+
```bash
|
|
79
|
+
TAG=v0.62.0
|
|
80
|
+
TARGET=x86_64-unknown-linux-musl
|
|
81
|
+
gh release download "$TAG" --repo pulseengine/meld --pattern "meld-${TAG}-${TARGET}.tar.gz"
|
|
82
|
+
tar xzf "meld-${TAG}-${TARGET}.tar.gz"
|
|
83
|
+
./meld-${TAG}-${TARGET}/meld --version
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
Verify what you downloaded before running it — see
|
|
87
|
+
[Verifying a Release](#verifying-a-release).
|
|
88
|
+
|
|
89
|
+
### From source
|
|
90
|
+
|
|
91
|
+
```bash
|
|
92
|
+
# From source (Cargo) — the only build for meld itself
|
|
93
|
+
cargo install --path meld-cli
|
|
94
|
+
|
|
95
|
+
# Fuse two components
|
|
96
|
+
meld fuse component_a.wasm component_b.wasm -o fused.wasm
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
### Full Pipeline
|
|
100
|
+
|
|
101
|
+
```bash
|
|
102
|
+
# 1. Build components
|
|
103
|
+
cargo component build --release
|
|
104
|
+
|
|
105
|
+
# 2. Fuse into single module
|
|
106
|
+
meld fuse composed.wasm -o fused.wasm
|
|
107
|
+
|
|
108
|
+
# 3. Optimize with Loom
|
|
109
|
+
loom optimize fused.wasm -o optimized.wasm
|
|
110
|
+
|
|
111
|
+
# 4. Run
|
|
112
|
+
wasmtime run optimized.wasm
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
### Bazel Integration
|
|
116
|
+
|
|
117
|
+
```starlark
|
|
118
|
+
load("@meld//rules:meld.bzl", "meld_fuse")
|
|
119
|
+
|
|
120
|
+
meld_fuse(
|
|
121
|
+
name = "my_app",
|
|
122
|
+
components = [
|
|
123
|
+
":component_a",
|
|
124
|
+
":component_b",
|
|
125
|
+
],
|
|
126
|
+
# Mandatory: the meld binary that will be recorded as the producer in the
|
|
127
|
+
# fused artifact's attestation. There is deliberately no default — the old
|
|
128
|
+
# one pointed at a Bazel self-build that stamped a version matching nothing
|
|
129
|
+
# (#406).
|
|
130
|
+
meld = "@meld_release//:meld",
|
|
131
|
+
)
|
|
132
|
+
```
|
|
133
|
+
|
|
134
|
+
`meld_fuse` is for projects that build *their* components with Bazel. It is not
|
|
135
|
+
exercised by meld's own CI, so treat it as community-supported.
|
|
136
|
+
|
|
137
|
+
## How It Works
|
|
138
|
+
|
|
139
|
+
1. **Parse** — Extract core modules and type information from components
|
|
140
|
+
2. **Resolve** — Build import/export graph, identify cross-component calls
|
|
141
|
+
3. **Merge** — Combine function/memory/table/global index spaces
|
|
142
|
+
4. **Adapt** — Generate Canonical ABI trampolines for cross-component calls
|
|
143
|
+
5. **Encode** — Output single core WebAssembly module
|
|
144
|
+
|
|
145
|
+
### Adapter Generation
|
|
146
|
+
|
|
147
|
+
Cross-component calls may require adapters that handle string transcoding (UTF-8, UTF-16, Latin-1), memory copying between component memories, list/array serialization, and resource handle transfer. Meld generates these adapters using techniques inspired by Wasmtime's FACT (Fused Adapter Compiler of Trampolines).
|
|
148
|
+
|
|
149
|
+
## Memory Strategies
|
|
150
|
+
|
|
151
|
+
### Auto (Default)
|
|
152
|
+
|
|
153
|
+
Always selects multi-memory, the strategy that is sound for every input. Auto never selects shared memory or address rebasing on its own (#326, #409); both remain available explicitly via `--memory shared --address-rebase`. The fused module therefore keeps one linear memory per input component, needs `wasm-opt --enable-multimemory` downstream, and has no single-address-space (MCU) lowering (issue #172).
|
|
154
|
+
|
|
155
|
+
```bash
|
|
156
|
+
meld fuse a.wasm b.wasm -o fused.wasm
|
|
157
|
+
wasm-opt -Os --enable-multimemory fused.wasm -o fused.opt.wasm
|
|
158
|
+
```
|
|
159
|
+
|
|
160
|
+
### Multi-Memory
|
|
161
|
+
|
|
162
|
+
Each component retains its own linear memory. Cross-component calls use adapters that allocate in the callee's memory via `cabi_realloc` and copy data with `memory.copy`. Requires multi-memory support (WebAssembly Core Spec 3.0) — downstream tools need `wasm-opt --enable-multimemory`, and single-address-space (MCU) targets have no lowering for it.
|
|
163
|
+
|
|
164
|
+
```bash
|
|
165
|
+
meld fuse --memory multi a.wasm b.wasm -o fused.wasm
|
|
166
|
+
```
|
|
167
|
+
|
|
168
|
+
### Shared Memory
|
|
169
|
+
|
|
170
|
+
All components share a single linear memory; pair with `--address-rebase`. Unsound if any component uses `memory.grow` — one component's growth corrupts every other component's address space, which is why `auto` never selects this form on its own.
|
|
171
|
+
|
|
172
|
+
```bash
|
|
173
|
+
meld fuse --memory shared --address-rebase a.wasm b.wasm -o fused.wasm
|
|
174
|
+
```
|
|
175
|
+
|
|
176
|
+
### Further `fuse` Options
|
|
177
|
+
|
|
178
|
+
Options for single-address-space targets and for auditing a fusion; the first three require `--memory shared`. Run `meld fuse --help` for the full text of each.
|
|
179
|
+
|
|
180
|
+
| Flag | Effect |
|
|
181
|
+
|------|--------|
|
|
182
|
+
| `--pack-rebase` | Place each component at its used data extent (16-byte aligned) instead of its declared page count, and size the merged memory to the packed total. Implies `--address-rebase`. Opt-in; sound only when a component references no address above its last data segment. |
|
|
183
|
+
| `--share-stack` | Collapse the per-provider shadow stacks into one shared region. Implies `--pack-rebase`. Requires every provider to carry a `__heap_base` marker and be stack-first, and fails loudly otherwise. Opt-in; sound only for non-reentrant, single-threaded, mutually non-calling providers. |
|
|
184
|
+
| `--domain NAME=INPUT[,INPUT...]` | Group inputs into memory domains: fuse within a domain, keep the Canonical ABI between domains. Repeat once per domain; every input must be named in exactly one. A domain is a trust boundary and is recorded in the attestation. |
|
|
185
|
+
| `--profile safety` | Require safety-relevant properties to be stated rather than inferred. Today this means `--memory` must be given: `auto` is refused. Output is byte-identical to the same explicit invocation under the default `--profile ecosystem`. |
|
|
186
|
+
| `--explain` | Report, for every fused cross-component call, the call-lowering class chosen (direct, memory-copy, transcode, async-lift) and how it was wired. The same records are embedded in the attestation. |
|
|
187
|
+
| `--emit-manifest` | Emit a `meld.signature-manifest` section giving, per export, the WIT and core signatures, the flattened parameter count, and the memory, allocator and post-return a host must use to invoke it. Opt-in. |
|
|
188
|
+
| `--exports <all\|world>` | Which exports the fused core module keeps. `all` (default) keeps every export of every inner module. `world` keeps only the functions that implement the outer world of the input(s), traced through their `canon lift`s (never by name) and exported under their world name `<interface>#<function>`, plus what the kept surface and the imports the module still has need: the memory and realloc of the kept lifts and of every `canon lower` behind a remaining import (a realloc nothing exports is exported as `meld:realloc/<component>`), `cabi_post_*`, the `[dtor]` exports of resources still imported, and the start function. Drops the internal interfaces of a composition, `__data_end`, `__heap_base` and every other global or table export. Only the export list changes; function bodies stay. A world function that cannot be traced to an exported fused function is an error. Not valid with `--component`. Recorded in the attestation. |
|
|
189
|
+
| `--reproducible` | Produce a byte-reproducible artifact: the attestation id is derived from the output content and the timestamp from `SOURCE_DATE_EPOCH` (default 0). Attested input names are replaced by positional identifiers (`component-0`, ...). |
|
|
190
|
+
| `--opaque-rep IFACE.RESOURCE` | Mark a resource as opaque-rep, for re-exporters whose representation is treated as a `u32` rather than a boxed pointer. Such resources skip the per-resource handle table layer. Repeatable. |
|
|
191
|
+
|
|
192
|
+
## Supply Chain Security
|
|
193
|
+
|
|
194
|
+
Meld integrates with [Sigil](https://github.com/pulseengine/sigil) for supply chain attestation. Each fusion operation records input component hashes, tool version and configuration, and transformation metadata. The attestation is embedded in the output module's custom section.
|
|
195
|
+
|
|
196
|
+
### Verifying a Release
|
|
197
|
+
|
|
198
|
+
Every tagged release ships with a CycloneDX SBOM, a cosign-signed `SHA256SUMS.txt`, and a SLSA v1 build-provenance attestation. To verify an installed binary against what GitHub Actions actually built:
|
|
199
|
+
|
|
200
|
+
```bash
|
|
201
|
+
# 1. Download an archive plus the signed checksum manifest from the release page.
|
|
202
|
+
TAG=v0.62.0
|
|
203
|
+
TARGET=x86_64-unknown-linux-gnu
|
|
204
|
+
gh release download "$TAG" --repo pulseengine/meld \
|
|
205
|
+
--pattern "meld-${TAG}-${TARGET}.tar.gz" \
|
|
206
|
+
--pattern 'SHA256SUMS.txt' \
|
|
207
|
+
--pattern 'SHA256SUMS.txt.cosign.bundle'
|
|
208
|
+
|
|
209
|
+
# 2. Verify SHA256SUMS.txt was signed by meld's release workflow (Sigstore keyless).
|
|
210
|
+
cosign verify-blob \
|
|
211
|
+
--certificate-identity-regexp \
|
|
212
|
+
'https://github.com/pulseengine/meld/.github/workflows/release.yml@.*' \
|
|
213
|
+
--certificate-oidc-issuer \
|
|
214
|
+
'https://token.actions.githubusercontent.com' \
|
|
215
|
+
--bundle SHA256SUMS.txt.cosign.bundle \
|
|
216
|
+
SHA256SUMS.txt
|
|
217
|
+
|
|
218
|
+
# 3. Verify the archive's digest is in the signed manifest.
|
|
219
|
+
sha256sum --ignore-missing -c SHA256SUMS.txt
|
|
220
|
+
|
|
221
|
+
# 4. (Optional) Verify the SLSA v1 build provenance attestation.
|
|
222
|
+
gh attestation verify "meld-${TAG}-${TARGET}.tar.gz" --repo pulseengine/meld
|
|
223
|
+
```
|
|
224
|
+
|
|
225
|
+
Step 2 proves the checksum file came from this repo's `release.yml`; step 3 ties the archive on disk to that signed manifest; step 4 independently confirms the archive was built by the same workflow run via GitHub's attestation API. Each release also includes a `meld-<version>.cdx.json` (CycloneDX SBOM, transitively covered by the signature on `SHA256SUMS.txt`) and `build-env.txt` capturing the runner toolchain versions.
|
|
226
|
+
|
|
227
|
+
## Formal Verification
|
|
228
|
+
|
|
229
|
+
Meld's **core** transformations carry mechanized Rocq proofs — 357 closed proofs (`Qed`) across the resolver, merger, adapter, and specification layers (see [`proofs/STATUS.md`](proofs/STATUS.md) for the per-stage coverage matrix). This is real, substantial verification on the core; it is **not** yet a whole-pipeline proof: the parser, rewriter, segments, and attestation stages are specified but their proofs are placeholders, orchestration (`lib.rs`) is unproven, and the semantic-preservation result is a **forward** simulation (the fused module simulates the original graph step-by-step; the reverse direction and the backward half of trap-equivalence are not yet proved).
|
|
230
|
+
|
|
231
|
+
Proven properties (Rocq):
|
|
232
|
+
- **Merge correctness** — Index remapping preserves function/memory/table references (injectivity, completeness, boundedness); memory-layout disjointness.
|
|
233
|
+
- **Resolve correctness** — Topological sort produces a valid instantiation order; cycle detection terminates.
|
|
234
|
+
- **Adapter correctness** — Canonical-ABI lift/lower roundtrip and crossing-adapter semantics (no `Admitted` lemmas remain in `proofs/`).
|
|
235
|
+
- **Forward simulation** — The fused module simulates the original component graph step-by-step (forward direction; fully proved).
|
|
236
|
+
|
|
237
|
+
In addition, the Canonical-ABI layout invariants (size/alignment saturating arithmetic, the #141 stream ring model) carry **Kani** bounded-model-checking harnesses (`abi_proofs.rs`, `resolver.rs`, `merger/`) that were `VERIFICATION SUCCESSFUL` locally (SR-40); these are **not gated in CI** (the shared runners do not ship the Kani toolchain), and the ABI size/alignment and aggregate-padding contracts that did not converge in CBMC fall back to unit tests.
|
|
238
|
+
|
|
239
|
+
Proofs are built via Bazel using [`rules_rocq_rust`](https://github.com/pulseengine/rules_rocq_rust):
|
|
240
|
+
|
|
241
|
+
```bash
|
|
242
|
+
bazel build //proofs/transformations/merge:merge_spec
|
|
243
|
+
bazel build //proofs/spec:fusion_spec
|
|
244
|
+
```
|
|
245
|
+
|
|
246
|
+
See [`proofs/`](proofs/) for the full proof tree and [`PROOF_GUIDE.md`](proofs/PROOF_GUIDE.md) for an introduction.
|
|
247
|
+
|
|
248
|
+
> [!NOTE]
|
|
249
|
+
> **Cross-cutting verification** — Rocq mechanized proofs, Kani bounded model checking, Z3 SMT verification, and Verus Rust verification are used across the PulseEngine toolchain. Sigil attestation chains bind it all together.
|
|
250
|
+
|
|
251
|
+
## Limitations
|
|
252
|
+
|
|
253
|
+
- **Resources** — Resource handle transfer across components is limited
|
|
254
|
+
- **Async** — P3 async lowering (`stream<T>`, `future<T>`, async lift/lower) is partial; async cross-component calls are covered only for the shapes exercised by the test suite, and the full async surface is not yet supported
|
|
255
|
+
- **String transcoding** — all pairs of UTF-8, UTF-16 and `latin1+utf16` are implemented for synchronous calls; async cross-encoding transcoding covers a bounded set of types (nested `list<list<string>>` to depth 2)
|
|
256
|
+
|
|
257
|
+
## Development
|
|
258
|
+
|
|
259
|
+
```bash
|
|
260
|
+
cargo build # Build
|
|
261
|
+
cargo test # Test
|
|
262
|
+
bazel build //proofs/... # Rocq proofs only (there is no Bazel build of meld)
|
|
263
|
+
RUST_LOG=debug cargo run -- fuse a.wasm b.wasm -o out.wasm
|
|
264
|
+
```
|
|
265
|
+
|
|
266
|
+
### Benchmarks
|
|
267
|
+
|
|
268
|
+
Criterion benchmarks for the fusion pipeline live in
|
|
269
|
+
`meld-core/benches/fusion_benchmarks.rs` and exercise four groups:
|
|
270
|
+
|
|
271
|
+
- `parser` — `ComponentParser::parse` throughput per input byte.
|
|
272
|
+
- `merger` — `Merger::merge` throughput per component count.
|
|
273
|
+
- `resolver` — `Resolver::resolve_with_hints` throughput per resolved-symbol count.
|
|
274
|
+
- `end_to_end` — `Fuser::fuse_with_stats` over small / medium / large
|
|
275
|
+
graphs.
|
|
276
|
+
|
|
277
|
+
```bash
|
|
278
|
+
cargo bench -p meld-core # full run
|
|
279
|
+
cargo bench -p meld-core --bench fusion_benchmarks -- parser # one group
|
|
280
|
+
cargo bench -p meld-core --no-run # compile-only sanity (CI smoke)
|
|
281
|
+
```
|
|
282
|
+
|
|
283
|
+
CI runs `cargo bench --no-run` on every PR (`.github/workflows/bench.yml`)
|
|
284
|
+
to prevent the bench harness from rotting. Full benches are not run in CI
|
|
285
|
+
to keep PRs fast and avoid noisy regressions on shared runners.
|
|
286
|
+
|
|
287
|
+
## License
|
|
288
|
+
|
|
289
|
+
Apache-2.0
|
|
290
|
+
|
|
291
|
+
---
|
|
292
|
+
|
|
293
|
+
<div align="center">
|
|
294
|
+
|
|
295
|
+
<sub>Part of <a href="https://github.com/pulseengine">PulseEngine</a> — formally verified WebAssembly toolchain for safety-critical systems</sub>
|
|
296
|
+
|
|
297
|
+
</div>
|
|
@@ -0,0 +1,5 @@
|
|
|
1
|
+
meld_cli-0.65.1.data/scripts/meld,sha256=6E4tr4TW0in-eOBxnahnLJoJJy6GH50JiUAyZfIoS7A,4258872
|
|
2
|
+
meld_cli-0.65.1.dist-info/METADATA,sha256=ORqYGrrdMJRJdJdFIcxpo16xEVryDo2GirVtWyXweXU,16496
|
|
3
|
+
meld_cli-0.65.1.dist-info/WHEEL,sha256=zGQuJXj2LtlHwMtp3BOAFbsoMkAmDkhsM7HVFzAMNPE,139
|
|
4
|
+
meld_cli-0.65.1.dist-info/licenses/LICENSE,sha256=euNbGsHkpv7jogDaNA58ccnfoNyAwgVCADOLGNlgIt8,10280
|
|
5
|
+
meld_cli-0.65.1.dist-info/RECORD,,
|
|
@@ -0,0 +1,190 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to the Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
Copyright 2024 PulseEngine
|
|
179
|
+
|
|
180
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
181
|
+
you may not use this file except in compliance with the License.
|
|
182
|
+
You may obtain a copy of the License at
|
|
183
|
+
|
|
184
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
185
|
+
|
|
186
|
+
Unless required by applicable law or agreed to in writing, software
|
|
187
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
188
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
189
|
+
See the License for the specific language governing permissions and
|
|
190
|
+
limitations under the License.
|