napier 0.1.0__tar.gz

napier-0.1.0/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,43 @@
+name: Bug report
+description: Something napier did wrong, or a crash
+labels: [bug]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for the report. Please leave out personal details (names, paths with your user name,
+        your own notes) and don't attach manuals. A security problem goes to the private form
+        instead: Security tab, "Report a vulnerability".
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened
+      description: The command you ran and what it did. Paste the error or traceback if there was one.
+      render: text
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: What you expected
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: napier --version
+      placeholder: napier 0.1.0 (from /path/to/napier)
+    validations:
+      required: true
+  - type: input
+    id: os
+    attributes:
+      label: OS and Python version
+      placeholder: macOS 15.3 (Apple silicon), Python 3.12.8
+    validations:
+      required: true
+  - type: input
+    id: extras
+    attributes:
+      label: Extras installed
+      placeholder: none, index, mcp

napier-0.1.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Questions and ideas
+    url: https://github.com/bvk7787/napier/discussions
+    about: How do I..., is my gear covered, show what you built. Issues are for bugs and requests.
+  - name: Report a security problem
+    url: https://github.com/bvk7787/napier/security/advisories/new
+    about: Privately, as SECURITY.md describes. Please don't open a public issue for it.

napier-0.1.0/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,21 @@
+name: Feature request
+description: An idea for napier
+labels: [enhancement]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: What you're trying to do
+      description: The problem or the workflow behind it.
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: What you'd like
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: What you've tried or considered

napier-0.1.0/.github/ISSUE_TEMPLATE/publisher_request.yml

@@ -0,0 +1,41 @@
+name: Publisher request
+description: For makers and publishers. Ask to remove, shorten or correct what napier lists from your documents
+labels: [publisher-request]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for getting in touch. docs/data-policy.md says what napier holds (links, checksums and
+        short quoted anchors; each user downloads the documents) and what you can ask for. A
+        maintainer answers within a week; removals are made first and discussed after.
+  - type: input
+    id: who
+    attributes:
+      label: Who you are
+      description: The company or publisher, and your role (or that you speak for them).
+    validations:
+      required: true
+  - type: textarea
+    id: what
+    attributes:
+      label: What it concerns
+      description: Source ids from sources.yaml, URLs, or the devices.
+    validations:
+      required: true
+  - type: dropdown
+    id: ask
+    attributes:
+      label: What you'd like
+      multiple: true
+      options:
+        - Remove the source entry, with its facts and anchors
+        - Shorten or remove particular anchors
+        - Point the entry at a different URL
+        - Correct a claim, a version or a page
+        - Something else (below)
+    validations:
+      required: true
+  - type: textarea
+    id: details
+    attributes:
+      label: Details

napier-0.1.0/.github/ISSUE_TEMPLATE/source_request.yml

@@ -0,0 +1,35 @@
+name: Source request
+description: Ask for a manual, changelog or community document napier doesn't have yet
+labels: [source]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        If you own the device, a pull request adding the source is the fastest route (CONTRIBUTING.md
+        shows the three commands). Otherwise, the details below are what a source needs.
+  - type: input
+    id: device
+    attributes:
+      label: Device
+      placeholder: Maker and model
+    validations:
+      required: true
+  - type: input
+    id: url
+    attributes:
+      label: Where the document lives
+      description: The maker's own link (PDF, changelog page, GitHub releases), and its version.
+    validations:
+      required: true
+  - type: dropdown
+    id: kind
+    attributes:
+      label: Kind
+      options: [manual, changelog, community, code]
+    validations:
+      required: true
+  - type: textarea
+    id: notes
+    attributes:
+      label: Anything else
+      description: Firmware version you run, questions you'd want answered from it, facts you've checked on the hardware.

napier-0.1.0/.github/dependabot.yml

@@ -0,0 +1,12 @@
+# GitHub Actions only. The Python dependencies are lower bounds in pyproject.toml and locked in
+# uv.lock for CI, updated by hand (`uv lock --upgrade`); the repository's Dependabot security
+# updates open a PR for any locked version with a published advisory.
+version: 2
+updates:
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: monthly
+    groups:
+      actions:
+        patterns: ["*"]

napier-0.1.0/.github/pull_request_template.md

@@ -0,0 +1,14 @@
+## What this changes
+
+<!-- What and why. Link the issue if there is one (sources and facts for gear you own don't need one). -->
+
+## Checks
+
+- [ ] `pytest -q` and `ruff check src tests` pass, and a behavior change comes with a test
+- [ ] For a new source: `source add` passed robots.txt (no `--ignore-robots` unless the publisher said yes, explained above), the manual is pinned, and the page offset was checked
+- [ ] For new facts: status and printed pages are right; facts with `q` and `anchors` pass `napier eval --device <id>` (score above)
+- [ ] For `hardware` facts: what I checked on the device, and on which firmware, is described above
+- [ ] For specs: `napier specs check <name>` passes with the manual fetched
+- [ ] No personal data: no real person, private rig or rack; fixtures use invented names and `example.test` URLs
+- [ ] `rack export` and MCP JSON only gained fields; nothing renamed or removed
+- [ ] Docs and CHANGELOG.md updated where behavior changed

napier-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,139 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+# Actions minutes are free on a public repository and metered on a private one, where the
+# maintainer runs the same checks locally: every job skips while the repository is private.
+jobs:
+  test:
+    name: test (${{ matrix.os }}, ${{ matrix.python-version }})
+    if: ${{ !github.event.repository.private }}
+    runs-on: ${{ matrix.os }}
+    timeout-minutes: 15
+    env:
+      PYTHONNOUSERSITE: "1"
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - {os: ubuntu-latest, python-version: "3.11"}
+          - {os: ubuntu-latest, python-version: "3.12", coverage: true}
+          - {os: ubuntu-latest, python-version: "3.13"}
+          - {os: ubuntu-latest, python-version: "3.14"}
+          - {os: macos-latest, python-version: "3.12"}
+          - {os: macos-latest, python-version: "3.14"}
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+      # the versions in uv.lock, base + dev (which includes mcp): the tests need no network, models
+      # or manuals, so the [index] extra stays out
+      - name: Install (locked versions)
+        shell: bash
+        run: |
+          python -m pip install --upgrade pip uv
+          uv export --frozen --no-hashes --extra dev --no-emit-project > "$RUNNER_TEMP/requirements.lock.txt"
+          python -m pip install -r "$RUNNER_TEMP/requirements.lock.txt"
+          python -m pip install -e . --no-deps
+      - name: Lint
+        run: ruff check src tests
+      - name: Tests
+        if: ${{ !matrix.coverage }}
+        run: pytest -q
+      - name: Tests, with coverage
+        if: ${{ matrix.coverage }}
+        shell: bash
+        run: |
+          # 71% when this began (2026-10-13): the floor stops a drop, raise it as it climbs
+          pytest -q --cov --cov-report=term --cov-fail-under=70
+          coverage report --format=markdown >> "$GITHUB_STEP_SUMMARY"
+      - name: The CLI starts and finds its data
+        run: |
+          napier --version
+          napier status > /dev/null
+          napier source list --json > /dev/null
+          napier rack scenarios --brief
+
+  typecheck:
+    name: typecheck (mypy)
+    if: ${{ !github.event.repository.private }}
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        with:
+          python-version: "3.12"
+          cache: pip
+      - name: Install (locked versions)
+        shell: bash
+        run: |
+          python -m pip install --upgrade pip uv
+          uv export --frozen --no-hashes --extra dev --no-emit-project > "$RUNNER_TEMP/requirements.lock.txt"
+          python -m pip install -r "$RUNNER_TEMP/requirements.lock.txt"
+          python -m pip install -e . --no-deps
+      - name: mypy (settings in pyproject.toml)
+        run: mypy
+
+  package:
+    # what `pip install napier` gives someone who hasn't cloned: the sdist and wheel build, their
+    # metadata passes twine, and the installed command runs and points at the clone it needs
+    name: package (build, install, run)
+    if: ${{ !github.event.repository.private }}
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        with:
+          python-version: "3.12"
+          cache: pip
+      - name: Build the sdist and wheel
+        run: |
+          python -m pip install --upgrade pip uv
+          uv build
+          ls -l dist
+      - name: Check the metadata
+        run: uvx twine check --strict dist/*
+      - name: Check what the sdist holds
+        shell: bash
+        run: |
+          tar tzf dist/*.tar.gz > "$RUNNER_TEMP/sdist.txt"
+          for f in sources.yaml facts/ specs/ catalog/modules.yaml examples/racks/layout.yaml LICENSE NOTICE uv.lock; do
+            grep -q "$f" "$RUNNER_TEMP/sdist.txt" || { echo "missing from the sdist: $f"; exit 1; }
+          done
+          if grep -q "/local/" "$RUNNER_TEMP/sdist.txt"; then echo "the sdist holds a local/ overlay"; exit 1; fi
+      - name: Install the wheel into a clean venv
+        run: |
+          python -m venv "$RUNNER_TEMP/venv"
+          "$RUNNER_TEMP/venv/bin/pip" install dist/*.whl
+      - name: The installed command says where to get the data
+        working-directory: ${{ runner.temp }}     # away from the checkout
+        shell: bash
+        run: |
+          export PATH="$RUNNER_TEMP/venv/bin:$PATH" NAPIER_HOME="$RUNNER_TEMP/home"
+          napier --version
+          napier --help > /dev/null
+          if napier status > out.txt 2>&1; then echo "status should fail outside a clone"; exit 1; fi
+          cat out.txt
+          grep -q "git clone https://github.com/bvk7787/napier" out.txt
+          if grep -q Traceback out.txt; then exit 1; fi

napier-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,65 @@
+name: Release
+
+# A version tag (v0.1.0) builds the package and publishes it to PyPI with Trusted Publishing:
+# no token is stored anywhere. PyPI trusts this workflow once the project's trusted publisher
+# names it (github.com/bvk7787/napier, workflow release.yml, environment pypi).
+# The tag must match the version in pyproject.toml. Nothing runs while the repository is private.
+
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    if: ${{ !github.event.repository.private }}
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        with:
+          python-version: "3.12"
+      - name: The tag matches the version
+        if: startsWith(github.ref, 'refs/tags/')
+        shell: bash
+        run: |
+          want="v$(python -c 'import tomllib; print(tomllib.load(open("pyproject.toml","rb"))["project"]["version"])')"
+          [ "$GITHUB_REF_NAME" = "$want" ] || { echo "tag $GITHUB_REF_NAME, pyproject says $want"; exit 1; }
+      - name: Build the sdist and wheel
+        run: |
+          python -m pip install --upgrade pip build twine
+          python -m build
+          twine check --strict dist/*
+      - name: The wheel installs and runs
+        shell: bash
+        run: |
+          python -m venv "$RUNNER_TEMP/v"
+          "$RUNNER_TEMP/v/bin/pip" install dist/*.whl
+          "$RUNNER_TEMP/v/bin/napier" --version
+      - uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    if: ${{ !github.event.repository.private && startsWith(github.ref, 'refs/tags/') }}
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    environment:
+      name: pypi
+      url: https://pypi.org/project/napier/
+    permissions:
+      id-token: write            # Trusted Publishing: PyPI checks this workflow's identity
+    steps:
+      - uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2

napier-0.1.0/.github/workflows/scorecard.yml

@@ -0,0 +1,41 @@
+name: Scorecard
+
+# OpenSSF Scorecard: checks the repository's security practices (branch protection, pinned
+# actions, token permissions, signed releases, and more) and publishes the score for the
+# README badge. Results land in the Security tab under Code scanning.
+
+on:
+  push:
+    branches: [main]
+  schedule:
+    - cron: "17 6 * * 1"          # Mondays
+  branch_protection_rule:
+  workflow_dispatch:
+
+permissions: read-all
+
+jobs:
+  analysis:
+    name: Scorecard analysis
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    permissions:
+      security-events: write      # upload the results to code scanning
+      id-token: write             # publish the results (and the badge)
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: ossf/scorecard-action@2d1146689b8cda280b9bc96326124645441f03bc # v2.4.4
+        with:
+          results_file: results.sarif
+          results_format: sarif
+          publish_results: true
+      - uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        with:
+          name: scorecard-results
+          path: results.sarif
+          retention-days: 5
+      - uses: github/codeql-action/upload-sarif@2892aa5e19bbd11bc0cff5427e3b750a04d9e3c2 # v4.38.2
+        with:
+          sarif_file: results.sarif

napier-0.1.0/.gitignore

@@ -0,0 +1,15 @@
+__pycache__/
+*.pyc
+.venv/
+.pytest_cache/
+*.egg-info/
+dist/
+build/
+.DS_Store
+# the private overlay (its own repo) and private agent notes
+/local/
+/CLAUDE.local.md
+.coverage
+coverage.xml
+.mypy_cache/
+.ruff_cache/

napier-0.1.0/AGENTS.md

@@ -0,0 +1,13 @@
+# Instructions for coding agents
+
+Helping someone *use* napier (look something up, add a source, check a fact, plan a rack)? Use the
+CLI or the MCP tools and cite what they print: title, version, printed page. Changing its code or
+data? Read on.
+
+- Read [CLAUDE.md](CLAUDE.md) first: the ground rules (polite fetching, printed pages, facts are
+  refuted rather than deleted, nothing personal in the public tree), the layout, and the checks to
+  run.
+- Contributing (tests, what a pull request needs): [CONTRIBUTING.md](CONTRIBUTING.md).
+- The rack planner and rack-source plug-ins: [docs/rack.md](docs/rack.md).
+- Never move data from a user's overlay (`local/`) into the public tree, and never write names,
+  rack URLs or rig notes into public files or commit messages.

napier-0.1.0/CHANGELOG.md

@@ -0,0 +1,44 @@
+# Changelog
+
+All notable changes to napier are recorded here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and versions follow
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html) (before 1.0, a minor version may change
+the CLI or the data formats).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-10-13
+
+First public release.
+
+### Added
+
+- Sources: manuals, firmware changelogs, forum snapshots, pinned firmware source and your own notes,
+  with printed-page offsets detected from the page footers. 149 sources for 101 devices ship with it.
+- `grep` and `read` over a text layer (one unit per printed page or section), and hybrid `search`
+  (vectors and BM25, fused, reranked) with pinned model revisions. Every result cites title,
+  version and printed page, and says which kind of source it came from.
+- The facts ledger (`manual`, `changelog`, `community`, `code`, `hardware`, `unverified`,
+  `refuted`) and `napier eval`, which fails below 90% hit@3.
+- `source check`, `source apply` and `facts recheck` for keeping sources current, and
+  `napier refresh`, an unattended pass for maintainers that opens a pull request.
+- An MCP server (`napier mcp`) with `status`, `search`, `grep`, `read`, `facts`, `add_fact`,
+  `verify_fact` and `rack`. Errors reach the assistant with their reason; `grep` and `search` list
+  the sources they couldn't search yet; facts it writes are stamped `via: mcp`.
+- A Eurorack rack planner: rack sources (built-in `file`, plug-ins under `napier.rack_sources`),
+  configurable case geometry, usage notes, what-if scenarios with power, distance and free-space
+  checks, manual-cited specs, and `rack view`.
+- A private overlay (`local/`) for your own sources, facts, rack and notes, merged at run time and
+  never committed to the public repository.
+- Polite fetching on every request: robots.txt per RFC 9309 (including `Crawl-delay` and
+  redirects), at least 2 seconds between requests to a site, backoff on 429 and 503, an honest user
+  agent. `fetch --from FILE` for documents a site doesn't allow napier to download.
+- Limits on what a source list or document can do: plain-name ids, http(s) only, no private or local
+  addresses, a 300 MB and 10-minute cap per download, and a guard against runaway regexes.
+- `napier status` summarizes per device (`--wide` for every source); unknown device or source ids
+  suggest the closest names.
+- docs: MCP setup for Claude Desktop, Claude Code, Cursor, VS Code, Codex and Windsurf; sources;
+  how it works; the rack planner; the data policy and a publisher request form.
+
+[Unreleased]: https://github.com/bvk7787/napier/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/bvk7787/napier/releases/tag/v0.1.0

napier-0.1.0/CITATION.cff

@@ -0,0 +1,11 @@
+cff-version: 1.2.0
+message: "If you refer to napier in writing, please cite it as below."
+title: "napier"
+abstract: "Page-cited lookups in music hardware manuals, changelogs and community documents, with a ledger of checked facts, a search eval and a Eurorack rack planner, as a CLI and an MCP server."
+type: software
+authors:
+  - name: "The napier authors"
+repository-code: "https://github.com/bvk7787/napier"
+license: Apache-2.0
+version: 0.1.0
+keywords: [music hardware, manuals, synthesizer, eurorack, mcp, search, citations]

napier-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,134 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement, the project's
+maintainers, privately through GitHub: use the repository's private reporting form
+(the **Security** tab, **Report a vulnerability**) and say that it is a conduct
+report, or report the content to GitHub with its **Report content** option.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations