emet 1.0.0__tar.gz

emet-1.0.0/AUTHORS.md

@@ -0,0 +1,12 @@
+# Authors
+
+## Author and Maintainer
+
+- Zain Dana Harper
+
+## AI Coding Contributor
+
+- Claude Code
+
+Zain Dana Harper reviews, tests, edits, and owns public release decisions,
+security posture, and final claims.

emet-1.0.0/LICENSE

@@ -0,0 +1,373 @@
+Mozilla Public License Version 2.0
+==================================
+
+1. Definitions
+--------------
+
+1.1. "Contributor"
+    means each individual or legal entity that creates, contributes to
+    the creation of, or owns Covered Software.
+
+1.2. "Contributor Version"
+    means the combination of the Contributions of others (if any) used
+    by a Contributor and that particular Contributor's Contribution.
+
+1.3. "Contribution"
+    means Covered Software of a particular Contributor.
+
+1.4. "Covered Software"
+    means Source Code Form to which the initial Contributor has attached
+    the notice in Exhibit A, the Executable Form of such Source Code
+    Form, and Modifications of such Source Code Form, in each case
+    including portions thereof.
+
+1.5. "Incompatible With Secondary Licenses"
+    means
+
+    (a) that the initial Contributor has attached the notice described
+        in Exhibit B to the Covered Software; or
+
+    (b) that the Covered Software was made available under the terms of
+        version 1.1 or earlier of the License, but not also under the
+        terms of a Secondary License.
+
+1.6. "Executable Form"
+    means any form of the work other than Source Code Form.
+
+1.7. "Larger Work"
+    means a work that combines Covered Software with other material, in
+    a separate file or files, that is not Covered Software.
+
+1.8. "License"
+    means this document.
+
+1.9. "Licensable"
+    means having the right to grant, to the maximum extent possible,
+    whether at the time of the initial grant or subsequently, any and
+    all of the rights conveyed by this License.
+
+1.10. "Modifications"
+    means any of the following:
+
+    (a) any file in Source Code Form that results from an addition to,
+        deletion from, or modification of the contents of Covered
+        Software; or
+
+    (b) any new file in Source Code Form that contains any Covered
+        Software.
+
+1.11. "Patent Claims" of a Contributor
+    means any patent claim(s), including without limitation, method,
+    process, and apparatus claims, in any patent Licensable by such
+    Contributor that would be infringed, but for the grant of the
+    License, by the making, using, selling, offering for sale, having
+    made, import, or transfer of either its Contributions or its
+    Contributor Version.
+
+1.12. "Secondary License"
+    means either the GNU General Public License, Version 2.0, the GNU
+    Lesser General Public License, Version 2.1, the GNU Affero General
+    Public License, Version 3.0, or any later versions of those
+    licenses.
+
+1.13. "Source Code Form"
+    means the form of the work preferred for making modifications.
+
+1.14. "You" (or "Your")
+    means an individual or a legal entity exercising rights under this
+    License. For legal entities, "You" includes any entity that
+    controls, is controlled by, or is under common control with You. For
+    purposes of this definition, "control" means (a) the power, direct
+    or indirect, to cause the direction or management of such entity,
+    whether by contract or otherwise, or (b) ownership of more than
+    fifty percent (50%) of the outstanding shares or beneficial
+    ownership of such entity.
+
+2. License Grants and Conditions
+--------------------------------
+
+2.1. Grants
+
+Each Contributor hereby grants You a world-wide, royalty-free,
+non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark)
+    Licensable by such Contributor to use, reproduce, make available,
+    modify, display, perform, distribute, and otherwise exploit its
+    Contributions, either on an unmodified basis, with Modifications, or
+    as part of a Larger Work; and
+
+(b) under Patent Claims of such Contributor to make, use, sell, offer
+    for sale, have made, import, and otherwise transfer either its
+    Contributions or its Contributor Version.
+
+2.2. Effective Date
+
+The licenses granted in Section 2.1 with respect to any Contribution
+become effective for each Contribution on the date the Contributor first
+distributes such Contribution.
+
+2.3. Limitations on Grant Scope
+
+The licenses granted in this Section 2 are the only rights granted under
+this License. No additional rights or licenses will be implied from the
+distribution or licensing of Covered Software under this License.
+Notwithstanding Section 2.1(b) above, no patent license is granted by a
+Contributor:
+
+(a) for any code that a Contributor has removed from Covered Software;
+    or
+
+(b) for infringements caused by: (i) Your and any other third party's
+    modifications of Covered Software, or (ii) the combination of its
+    Contributions with other software (except as part of its Contributor
+    Version); or
+
+(c) under Patent Claims infringed by Covered Software in the absence of
+    its Contributions.
+
+This License does not grant any rights in the trademarks, service marks,
+or logos of any Contributor (except as may be necessary to comply with
+the notice requirements in Section 3.4).
+
+2.4. Subsequent Licenses
+
+No Contributor makes additional grants as a result of Your choice to
+distribute the Covered Software under a subsequent version of this
+License (see Section 10.2) or under the terms of a Secondary License (if
+permitted under the terms of Section 3.3).
+
+2.5. Representation
+
+Each Contributor represents that the Contributor believes its
+Contributions are its original creation(s) or it has sufficient rights
+to grant the rights to its Contributions conveyed by this License.
+
+2.6. Fair Use
+
+This License is not intended to limit any rights You have under
+applicable copyright doctrines of fair use, fair dealing, or other
+equivalents.
+
+2.7. Conditions
+
+Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
+in Section 2.1.
+
+3. Responsibilities
+-------------------
+
+3.1. Distribution of Source Form
+
+All distribution of Covered Software in Source Code Form, including any
+Modifications that You create or to which You contribute, must be under
+the terms of this License. You must inform recipients that the Source
+Code Form of the Covered Software is governed by the terms of this
+License, and how they can obtain a copy of this License. You may not
+attempt to alter or restrict the recipients' rights in the Source Code
+Form.
+
+3.2. Distribution of Executable Form
+
+If You distribute Covered Software in Executable Form then:
+
+(a) such Covered Software must also be made available in Source Code
+    Form, as described in Section 3.1, and You must inform recipients of
+    the Executable Form how they can obtain a copy of such Source Code
+    Form by reasonable means in a timely manner, at a charge no more
+    than the cost of distribution to the recipient; and
+
+(b) You may distribute such Executable Form under the terms of this
+    License, or sublicense it under different terms, provided that the
+    license for the Executable Form does not attempt to limit or alter
+    the recipients' rights in the Source Code Form under this License.
+
+3.3. Distribution of a Larger Work
+
+You may create and distribute a Larger Work under terms of Your choice,
+provided that You also comply with the requirements of this License for
+the Covered Software. If the Larger Work is a combination of Covered
+Software with a work governed by one or more Secondary Licenses, and the
+Covered Software is not Incompatible With Secondary Licenses, this
+License permits You to additionally distribute such Covered Software
+under the terms of such Secondary License(s), so that the recipient of
+the Larger Work may, at their option, further distribute the Covered
+Software under the terms of either this License or such Secondary
+License(s).
+
+3.4. Notices
+
+You may not remove or alter the substance of any license notices
+(including copyright notices, patent notices, disclaimers of warranty,
+or limitations of liability) contained within the Source Code Form of
+the Covered Software, except that You may alter any license notices to
+the extent required to remedy known factual inaccuracies.
+
+3.5. Application of Additional Terms
+
+You may choose to offer, and to charge a fee for, warranty, support,
+indemnity or liability obligations to one or more recipients of Covered
+Software. However, You may do so only on Your own behalf, and not on
+behalf of any Contributor. You must make it absolutely clear that any
+such warranty, support, indemnity, or liability obligation is offered by
+You alone, and You hereby agree to indemnify every Contributor for any
+liability incurred by such Contributor as a result of warranty, support,
+indemnity or liability terms You offer. You may include additional
+disclaimers of warranty and limitations of liability specific to any
+jurisdiction.
+
+4. Inability to Comply Due to Statute or Regulation
+---------------------------------------------------
+
+If it is impossible for You to comply with any of the terms of this
+License with respect to some or all of the Covered Software due to
+statute, judicial order, or regulation then You must: (a) comply with
+the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must
+be placed in a text file included with all distributions of the Covered
+Software under this License. Except to the extent prohibited by statute
+or regulation, such description must be sufficiently detailed for a
+recipient of ordinary skill to be able to understand it.
+
+5. Termination
+--------------
+
+5.1. The rights granted under this License will terminate automatically
+if You fail to comply with any of its terms. However, if You become
+compliant, then the rights granted under this License from a particular
+Contributor are reinstated (a) provisionally, unless and until such
+Contributor explicitly and finally terminates Your grants, and (b) on an
+ongoing basis, if such Contributor fails to notify You of the
+non-compliance by some reasonable means prior to 60 days after You have
+come back into compliance. Moreover, Your grants from a particular
+Contributor are reinstated on an ongoing basis if such Contributor
+notifies You of the non-compliance by some reasonable means, this is the
+first time You have received notice of non-compliance with this License
+from such Contributor, and You become compliant prior to 30 days after
+Your receipt of the notice.
+
+5.2. If You initiate litigation against any entity by asserting a patent
+infringement claim (excluding declaratory judgment actions,
+counter-claims, and cross-claims) alleging that a Contributor Version
+directly or indirectly infringes any patent, then the rights granted to
+You by any and all Contributors for the Covered Software under Section
+2.1 of this License shall terminate.
+
+5.3. In the event of termination under Sections 5.1 or 5.2 above, all
+end user license agreements (excluding distributors and resellers) which
+have been validly granted by You or Your distributors under this License
+prior to termination shall survive termination.
+
+************************************************************************
+*                                                                      *
+*  6. Disclaimer of Warranty                                           *
+*  -------------------------                                           *
+*                                                                      *
+*  Covered Software is provided under this License on an "as is"       *
+*  basis, without warranty of any kind, either expressed, implied, or  *
+*  statutory, including, without limitation, warranties that the       *
+*  Covered Software is free of defects, merchantable, fit for a        *
+*  particular purpose or non-infringing. The entire risk as to the     *
+*  quality and performance of the Covered Software is with You.        *
+*  Should any Covered Software prove defective in any respect, You     *
+*  (not any Contributor) assume the cost of any necessary servicing,   *
+*  repair, or correction. This disclaimer of warranty constitutes an   *
+*  essential part of this License. No use of any Covered Software is   *
+*  authorized under this License except under this disclaimer.         *
+*                                                                      *
+************************************************************************
+
+************************************************************************
+*                                                                      *
+*  7. Limitation of Liability                                          *
+*  --------------------------                                          *
+*                                                                      *
+*  Under no circumstances and under no legal theory, whether tort      *
+*  (including negligence), contract, or otherwise, shall any           *
+*  Contributor, or anyone who distributes Covered Software as          *
+*  permitted above, be liable to You for any direct, indirect,         *
+*  special, incidental, or consequential damages of any character      *
+*  including, without limitation, damages for lost profits, loss of    *
+*  goodwill, work stoppage, computer failure or malfunction, or any    *
+*  and all other commercial damages or losses, even if such party      *
+*  shall have been informed of the possibility of such damages. This   *
+*  limitation of liability shall not apply to liability for death or   *
+*  personal injury resulting from such party's negligence to the       *
+*  extent applicable law prohibits such limitation. Some               *
+*  jurisdictions do not allow the exclusion or limitation of           *
+*  incidental or consequential damages, so this exclusion and          *
+*  limitation may not apply to You.                                    *
+*                                                                      *
+************************************************************************
+
+8. Litigation
+-------------
+
+Any litigation relating to this License may be brought only in the
+courts of a jurisdiction where the defendant maintains its principal
+place of business and such litigation shall be governed by laws of that
+jurisdiction, without reference to its conflict-of-law provisions.
+Nothing in this Section shall prevent a party's ability to bring
+cross-claims or counter-claims.
+
+9. Miscellaneous
+----------------
+
+This License represents the complete agreement concerning the subject
+matter hereof. If any provision of this License is held to be
+unenforceable, such provision shall be reformed only to the extent
+necessary to make it enforceable. Any law or regulation which provides
+that the language of a contract shall be construed against the drafter
+shall not be used to construe this License against a Contributor.
+
+10. Versions of the License
+---------------------------
+
+10.1. New Versions
+
+Mozilla Foundation is the license steward. Except as provided in Section
+10.3, no one other than the license steward has the right to modify or
+publish new versions of this License. Each version will be given a
+distinguishing version number.
+
+10.2. Effect of New Versions
+
+You may distribute the Covered Software under the terms of the version
+of the License under which You originally received the Covered Software,
+or under the terms of any subsequent version published by the license
+steward.
+
+10.3. Modified Versions
+
+If you create software not governed by this License, and you want to
+create a new license for such software, you may create and use a
+modified version of this License if you rename the license and remove
+any references to the name of the license steward (except to note that
+such modified license differs from this License).
+
+10.4. Distributing Source Code Form that is Incompatible With Secondary
+Licenses
+
+If You choose to distribute Source Code Form that is Incompatible With
+Secondary Licenses under the terms of this version of the License, the
+notice described in Exhibit B of this License must be attached.
+
+Exhibit A - Source Code Form License Notice
+-------------------------------------------
+
+  This Source Code Form is subject to the terms of the Mozilla Public
+  License, v. 2.0. If a copy of the MPL was not distributed with this
+  file, You can obtain one at https://mozilla.org/MPL/2.0/.
+
+If it is not possible or desirable to put the notice in a particular
+file, then You may include the notice in a location (such as a LICENSE
+file in a relevant directory) where a recipient would be likely to look
+for such a notice.
+
+You may add additional accurate notices of copyright ownership.
+
+Exhibit B - "Incompatible With Secondary Licenses" Notice
+---------------------------------------------------------
+
+  This Source Code Form is "Incompatible With Secondary Licenses", as
+  defined by the Mozilla Public License, v. 2.0.

emet-1.0.0/PKG-INFO

@@ -0,0 +1,228 @@
+Metadata-Version: 2.4
+Name: emet
+Version: 1.0.0
+Summary: A small external witness for AI oversight: re-derive the bytes, get MATCH / DRIFT / UNVERIFIABLE, trust nothing in-band.
+Author: HarperZ9
+License: MPL-2.0
+Project-URL: Homepage, https://github.com/HarperZ9/emet
+Project-URL: Repository, https://github.com/HarperZ9/emet
+Project-URL: Issues, https://github.com/HarperZ9/emet/issues
+Project-URL: Specification, https://github.com/HarperZ9/emet/blob/main/SPEC.md
+Keywords: integrity,witness,provenance,ai-oversight,attestation,re-derivability,supply-chain
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Mozilla Public License 2.0 (MPL 2.0)
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: AUTHORS.md
+Dynamic: license-file
+
+# EMET
+
+> A small external witness for AI oversight: re-derive the bytes, get one of three verdicts, trust nothing in-band.
+
+![EMET advisory integrity witness architecture](assets/emet-hero.png)
+
+[![license: MPL-2.0](https://img.shields.io/badge/license-MPL--2.0-blue.svg)](LICENSE)
+![python](https://img.shields.io/badge/python-3.x-blue.svg)
+![version](https://img.shields.io/badge/version-1.0.0-blue.svg)
+[![PyPI](https://img.shields.io/pypi/v/emet.svg)](https://pypi.org/project/emet/)
+[![CI](https://github.com/HarperZ9/emet/actions/workflows/conformance.yml/badge.svg)](https://github.com/HarperZ9/emet/actions/workflows/conformance.yml)
+![deps: none](https://img.shields.io/badge/deps-none-success.svg)
+[![part of: AI-accountability toolkit](https://img.shields.io/badge/part_of-AI--accountability_toolkit-7a5cff.svg)](https://harperz9.github.io)
+
+EMET is a small external witness for AI oversight and source/view consistency.
+It checks whether bytes reaching a model still match the source they claim to
+represent, then reports one of three deliberately limited verdicts: `MATCH`,
+`DRIFT`, or `UNVERIFIABLE`.
+
+It exists for the gap build-provenance tools do not cover by themselves: a
+system vouching for itself in-band, a presented view drifting away from source,
+or a monitor reading a different file than the one that actually runs. Trust
+comes from re-derivation - same bytes, same answer - not from authority. There
+is no `TRUSTED` verdict.
+
+`emet` is Hebrew for "truth."
+
+## Why it matters
+
+EMET is an advisory integrity witness for AI work. Its public value is narrow
+and testable: it re-derives bytes, compares source and view material, and emits
+closed verdicts without claiming authority, safety, approval, or permission.
+
+That makes it useful anywhere Project Telos needs provenance without another
+self-attesting layer. A model-facing view can drift from its source; a monitor
+can observe the wrong artifact; a generated report can overstate what was
+checked. EMET gives those surfaces a small external witness that says what
+matched, what drifted, and what could not be verified.
+
+## Usage
+
+Run the core checks directly from a checkout:
+
+```sh
+python membrane.py selftest
+python conformance/run.py membrane.py
+python test_forward_delivery_contract.py
+```
+
+For complete command examples and captured outputs, see [USAGE.md](USAGE.md).
+
+## For developers
+
+Keep EMET small, external, and advisory. Before changing public-facing docs,
+conformance behavior, or witness adapters, run the targeted checks:
+
+```sh
+python test_forward_delivery_contract.py
+python test_membrane.py
+python conformance/run.py membrane.py
+python -m public_surface_sweeper . --workspace --json
+```
+
+Spec changes, conformance-vector changes, and implementation behavior must move
+together. EMET must not emit `TRUSTED`, `APPROVED`, `SAFE`, or any value that
+grants authority or permission.
+
+## What's here
+
+- A stdlib-only Python reference - `membrane.py` / `organs.py` / `monitor.py` / `corpus.py` / `verdict.py` / `report.py`, no dependencies; run it straight from a checkout or `pip install emet` for the `emet` console script.
+- A from-scratch Rust second implementation - `impl/rust/emet.rs`, no crates.
+- A clean-room Node.js third implementation - `impl/js/emet.js`, built-in modules only (no npm).
+- A clean-room Go fourth implementation - `impl/go/emet.go`, standard library only (no third-party modules).
+- A normative, frozen v1.0 spec, a language-agnostic conformance suite, a STRIDE threat model, and an in-toto attestation adapter.
+- A versioned marker corpus (`conformance/markers.corpus`) all four implementations load and re-derive identically.
+- All four implementations pass the same 35 conformance vectors in CI on every push - byte-hash core, the exit-code split, the `--json` envelope, the marker path, and the audit chain (write and verify).
+
+## Reproduce it
+
+```sh
+git clone https://github.com/HarperZ9/emet && cd emet
+python conformance/run.py membrane.py            # Python reference: 35/35
+( cd impl/rust && rustc -O emet.rs -o emet )     # build the Rust second implementation
+python conformance/run.py impl/rust/emet         # Rust:    35/35
+python conformance/run.py impl/js/emet.js        # Node.js: 35/35
+( cd impl/go && go build -o emet emet.go )       # build the Go fourth implementation
+python conformance/run.py impl/go/emet           # Go:      35/35
+```
+
+## Use it
+
+From a checkout with `python membrane.py <cmd>`, or after `pip install emet`
+with the `emet` console script - the two are equivalent:
+
+```sh
+emet selftest                       # re-derive its own hash (emet_self_sha256=)
+emet anchor  <path>...              # pin raw-byte hashes
+emet verify  <path>...              # MATCH / DRIFT / UNVERIFIABLE
+emet coherence <source> <view>      # is a presented view faithful to source?
+emet refuse  <file>                 # detect + strip in-band authority claims
+emet corroborate <path>             # read-path-diverse agreement
+emet audit                          # recompute the tamper-evident log chain
+emet <any> --json                   # machine-readable canonical envelope (exit code unchanged)
+```
+
+Exit codes (SPEC section 5): `0` held · `1` a difference found (DRIFT /
+VIEW_DIFFERS_FROM_SOURCE / QUARANTINE / BROKEN) · `2` UNVERIFIABLE · `3` markers ·
+`64` usage.
+
+For an install/build line, per-command worked examples with expected output, the
+companion tools (`monitor.py`, `organs.py`), and a runnable demo, see
+[USAGE.md](USAGE.md) and [examples/](examples/).
+
+## Proof-surface use
+
+EMET is the witness point in a proof-surface pipeline:
+
+```text
+source bytes -> presented view -> witness verdict -> reviewer handoff
+```
+
+Use it when a repo, report, model-facing prompt, or generated view needs a
+small external check that the presented material still matches the source it
+claims to represent.
+
+Fast reviewer checklist:
+
+- `MATCH` means the checked material re-derived to the expected byte-level
+  result.
+- `DRIFT` means the presented view or checked bytes changed.
+- `UNVERIFIABLE` means the witness cannot make the comparison.
+- There is no `TRUSTED` verdict.
+
+This makes EMET useful as a release-readiness and diligence artifact: it can
+show what was compared and what verdict was produced without asking the witness
+to become an authority.
+
+The optional `adapters/proof_surface_receipt.py` adapter emits compact JSON
+witness receipts for proof-index and release-readiness workflows. It lives
+outside the EMET core and does not change governed stdout, signing, enforcement,
+or actuation boundaries. The adapter only accepts governed verdict tokens as
+whole tokens and refuses authority-shaped stdout before it enters a receipt.
+
+## What it won't do
+
+It only reports facts. It can't say `TRUSTED`, doesn't decide whether a model is
+safe, runs outside whatever it audits, and never edits, signs, or blocks anything.
+Those constraints are the point, not limitations - see [SPEC.md](SPEC.md) section 6.
+
+## Status
+
+v1.0.0 - the spec is **frozen and stable** (v1.0.0). The byte-hash core, the
+exit-code split, the `--json` envelope, the marker path (a single versioned corpus
+matched identically across the implementations), and the audit chain (write and
+verify) all re-derive across four languages and are checked in CI (35 conformance
+vectors, all four implementations). What 1.0.0 asserts is exactly two things: the
+**contract is frozen**, and the **reference implementations are production-grade**.
+It deliberately does **not** claim re-derivability is *proven* - that is a distinct,
+still-open axis, stated plainly rather than papered over:
+
+- The Rust, Node.js, and Go implementations are same-author (two of them clean-room
+  from the spec alone), not independent.
+- SPEC section 12's actual bar - an *independent, different-author* implementation
+  passing the vectors - is not yet met, and per section 12 no party should treat
+  re-derivability as proven until it is.
+
+Freezing the contract and demonstrating independent re-derivation are orthogonal;
+conflating them would be the exact in-band overclaim EMET's `refuse` strips. For a
+tool whose only credential is reproduction, an inflated claim would refute itself -
+so the claim is scoped to exactly what CI reproduces today.
+
+## Call for an independent implementation
+
+EMET's only credential is reproduction: same bytes, same verdict. Four
+implementations (Python reference + Rust + Node.js + Go) already agree on all 31
+conformance vectors in CI - but they all share an author, so that agreement shows
+the spec is *implementable* (in four languages, from its text alone), not yet
+that it is *independently re-derivable*.
+
+The highest-leverage contribution is therefore not another language but a
+**different-author implementation, written from [SPEC.md](SPEC.md) alone** (not by
+reading the existing code), in any language, that passes `conformance/vectors.json`:
+
+```sh
+# build your implementation, then:
+python conformance/run.py ./your-emet     # expected: CONFORMANCE 35/35
+```
+
+Where your implementation and the spec disagree, **the spec is wrong** - open an
+issue; those divergences are the point. (Both clean-room ports already did exactly
+this: the Node.js impl surfaced that the marker *count* was unpinned - SPEC section
+16 and the `refuse-repeated-marker-occurrence-count` vector now pin it - and the Go
+impl surfaced the reason-code enum and default-JSON-encoder gaps, now pinned; see
+[docs/spec-findings-from-go-impl.md](docs/spec-findings-from-go-impl.md).) A
+different-author implementation is what converts re-derivability from *asserted* to
+*demonstrated* (SPEC section 12). Claim a language in [Discussions](../../discussions)
+so effort isn't duplicated.
+
+## Docs
+
+[SPEC.md](SPEC.md) · [RATIONALE.md](RATIONALE.md) (why EMET is shaped the way it is, derived from first principles) · [conformance/](conformance/) · [THREAT-MODEL.md](THREAT-MODEL.md) · [COVERAGE.json](COVERAGE.json) · [SECURITY.md](SECURITY.md) · [CONTRIBUTING.md](CONTRIBUTING.md)
+
+MPL-2.0.