modelmoat 0.1.0__tar.gz

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

@@ -0,0 +1,47 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+
+      - name: Lint
+        run: ruff check modelmoat tests
+
+      - name: Unit and fixture tests
+        run: pytest -q
+
+      # The two-sided behavior gate. A scanner that flags secure infrastructure
+      # is as broken as one that misses insecure infrastructure, so CI requires
+      # zero findings on the secure fixture and a failing exit code on the
+      # insecure one.
+      - name: Behavior gate - secure fixture must be clean
+        run: modelmoat scan tests/fixtures/secure
+
+      - name: Behavior gate - insecure fixture must fail the build
+        run: |
+          if modelmoat scan tests/fixtures/insecure --json > /dev/null; then
+            echo "Expected a non-zero exit code on the insecure fixture"
+            exit 1
+          fi

modelmoat-0.1.0/.gitignore

@@ -0,0 +1,14 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+.pytest_cache/
+.ruff_cache/
+.coverage
+coverage.xml
+.venv/
+venv/
+.terraform/
+findings.json

modelmoat-0.1.0/CLAUDE.md

@@ -0,0 +1,117 @@
+# CLAUDE.md
+
+Context for Claude Code sessions in this repository. Read this before making
+changes.
+
+## What this project is
+
+modelmoat is a static analysis tool that scans Terraform for AI infrastructure
+security misconfigurations: SageMaker networking, Bedrock and SageMaker IAM
+grants, model artifact buckets, missing PrivateLink for AI service traffic, and
+vector data store posture.
+
+Positioning, stated exactly this way and no stronger: general IaC scanners cover
+some of this ground, and modelmoat is the one that treats AI infrastructure as
+its own category. Never claim to be the first or only scanner with AI checks.
+That claim is false and the audience for this tool will check.
+
+The maintainer works in infrastructure security and is not a Terraform expert.
+Explain Terraform and AWS specifics when they matter to a decision, and do not
+assume familiarity with provider internals.
+
+## The one rule above all others
+
+The secure fixture must produce zero findings. A scanner that fires on correct
+infrastructure trains people to ignore it, and for this project the false
+positive rate is the product. CI enforces this in both directions on every push:
+`tests/fixtures/secure` must exit 0, `tests/fixtures/insecure` must exit
+non-zero.
+
+If a change makes the secure fixture produce a finding, the change is wrong. Do
+not adjust the fixture to make a check pass.
+
+## Rules every check follows
+
+1. Checks run against the whole `ProjectGraph`, never a single file. Terraform
+   spreads related resources across files and so do we.
+2. Values containing `${` are unknown and are never flagged. modelmoat does not
+   flag what it cannot prove.
+3. Keyword matching is on whole tokens, never substrings. `email` must not match
+   `ai` and `html` must not match `ml`. Both are permanent negative controls in
+   the test suite.
+4. Severity is calibrated to demonstrated exposure:
+   - CRITICAL: the configuration itself proves internet reachability with weak
+     or absent authentication, for example a bucket policy granting
+     `Principal "*"`.
+   - HIGH: missing encryption, or permissions broad enough to reach any AI
+     resource in the account.
+   - MEDIUM and LOW: hygiene. A missing S3 public access block is LOW, because
+     AWS account defaults have blocked public access on new buckets since April
+     2023.
+5. Finding messages never claim more than the configuration proves. A SageMaker
+   model outside a VPC is a runtime and traffic path exposure, not an open URL,
+   because invocation still requires a SigV4-signed IAM request. Say so.
+6. Every new check needs two fixtures: one that triggers it, and one that looks
+   similar but must stay silent.
+
+## Architecture
+
+- `modelmoat/graph.py` parses every `.tf` file once into a `ProjectGraph`.
+  Handles python-hcl2 8.x quirks: string literals and block labels come back
+  wrapped in literal quotes, and nested blocks come back as lists of dicts
+  tagged with `__is_block__`. Helpers: `unquote`, `normalize`, `blocks`,
+  `first_block`, `is_unknown`, `truthy`, `missing_or_false`, `ai_tokens_in`,
+  `extract_ref`.
+- `modelmoat/policy.py` parses IAM policy documents. Terraform expresses these
+  four ways: `jsonencode()` (which hcl2 serializes back in HCL syntax with `=`
+  instead of `:`, so it needs a transform before JSON parsing), raw JSON
+  heredocs, `data.aws_iam_policy_document` statement blocks, and managed policy
+  ARNs. Managed policy matching is case-insensitive on both sides.
+- `modelmoat/scanner.py` holds `Finding`, `ScanResult`, and the orchestrator.
+- `modelmoat/checks/` holds the five checks, registered in `checks/__init__.py`.
+- `modelmoat/cli.py` is Typer with an explicit `scan` subcommand. Exit code is
+  computed before severity filtering, so `--min-severity` changes what prints
+  without changing what fails a build.
+
+## Gotchas already paid for
+
+- python-hcl2 8.x does not support the `with_meta` keyword, so line numbers come
+  from a regex scan of the source, not the parser.
+- `vpc_config` lives on `aws_sagemaker_model`, not on
+  `aws_sagemaker_endpoint_configuration`. Checking the endpoint config fires on
+  every endpoint config ever written.
+- S3 public access block arguments default to false when omitted, not true.
+- Block Public Access overrides both ACLs and bucket policies, so a bucket with
+  all four protections enabled produces no finding regardless of its ACL.
+- CLI output uses a per-finding block layout, not a Rich table. Tables shred at
+  80 columns, which is what people see when piping output to a file.
+
+## Before committing
+
+    python -m pytest -q
+    python -m ruff check modelmoat tests
+
+Both must pass. Do not commit with failing tests or lint errors.
+
+## Writing style for anything user-facing
+
+Applies to README, docs, finding messages, release notes, issue replies, and any
+LinkedIn or blog drafts.
+
+Banned words: leverage, navigate, robust, seamless, foster, delve, landscape,
+tapestry, vibrant, nestled, underscore, harness, unleash, unlock, elevate,
+empower, streamline, pivotal, paradigm, holistic, synergy, ecosystem, journey,
+realm, sphere, arena, fabric, beacon, cornerstone, testament.
+
+Banned phrases: "not just X but Y", "it's important to note", "furthermore",
+"moreover", "in conclusion".
+
+Style: no em dashes. Lead with specific numbers. Paragraphs of three or four
+sentences at most. No rule-of-three lists. No emojis in headers. No stacked
+hedging. Never name the maintainer's employer.
+
+## Roadmap
+
+Pinecone and Weaviate providers, SARIF output for GitHub code scanning, Azure AI
+and Vertex AI resources, and a `--baseline` file so teams can adopt the tool on
+an existing codebase without a wall of findings on day one.

modelmoat-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,29 @@
+# Contributing
+
+Contributions are welcome, especially new checks and false positive reports.
+
+## Setup
+
+    pip install -e ".[dev]"
+    pytest
+
+## Rules for checks
+
+1. Every check runs against the whole project graph, not a single file.
+   Terraform spreads related resources across files and so do we.
+2. Every check needs two fixtures: one that triggers it and one that looks
+   similar but must not. The secure fixture returning zero findings is a hard
+   CI gate.
+3. Severity is calibrated to real exposure. Reachable-from-internet with weak
+   or no auth is CRITICAL. Missing encryption or broad IAM is HIGH. Hygiene
+   gaps are MEDIUM or LOW. A finding message must never claim more than the
+   configuration proves.
+4. Values that come from variables or expressions we cannot resolve are
+   treated as unknown and are not flagged.
+
+## Adding a check
+
+Create a module in `modelmoat/checks/`, implement a class with `check_id`,
+`check_name`, and `run(graph) -> list[Finding]`, register it in
+`modelmoat/checks/__init__.py`, and add both fixtures plus assertions in
+`tests/`.

modelmoat-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

modelmoat-0.1.0/PKG-INFO

@@ -0,0 +1,170 @@
+Metadata-Version: 2.5
+Name: modelmoat
+Version: 0.1.0
+Summary: Static analysis for AI infrastructure security in Terraform. Finds misconfigured SageMaker, Bedrock IAM, model artifact buckets, missing PrivateLink, and exposed vector databases before they deploy.
+Project-URL: Homepage, https://github.com/rashadlee/modelmoat
+Project-URL: Issues, https://github.com/rashadlee/modelmoat/issues
+Author: modelmoat contributors
+License: Apache-2.0
+License-File: LICENSE
+Keywords: ai-security,bedrock,iac,sagemaker,security,static-analysis,terraform
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: System Administrators
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Security
+Requires-Python: >=3.10
+Requires-Dist: python-hcl2<9,>=8.0
+Requires-Dist: rich>=13.0
+Requires-Dist: typer>=0.12
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.5; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# modelmoat
+
+Static analysis for AI infrastructure security in Terraform. It reads your `.tf`
+files and finds the misconfigurations that show up specifically when teams ship
+Bedrock, SageMaker, and vector databases: blanket `bedrock:*` grants, model
+artifact buckets open to the internet, embedding stores without encryption, and
+inference traffic that never touches your private network.
+
+General IaC scanners check hundreds of AWS resource types and cover some of this
+ground. modelmoat is the one that treats AI infrastructure as its own category,
+with checks written around how these services actually fail rather than a
+generic encryption rule applied to every database in the account.
+
+Findings run against the whole project at once, not file by file, because
+Terraform spreads related resources across files. A bucket in `s3.tf` and its
+public access block in `security.tf` are one decision, and modelmoat reads them
+that way.
+
+## Install
+
+    pipx install modelmoat
+
+Or with pip:
+
+    pip install modelmoat
+
+Python 3.10 or newer. modelmoat only reads local files. It never contacts your
+AWS account, reads state files, or touches credentials.
+
+## Usage
+
+    modelmoat scan .
+    modelmoat scan infra/ modules/ --min-severity HIGH
+    modelmoat scan . --json > findings.json
+
+Real output from the test fixtures in this repo:
+
+```
+modelmoat 0.1.0 scanned 6 Terraform file(s)
+  CRITICAL: 4  HIGH: 7  MEDIUM: 4  LOW: 3
+
+CRITICAL S3-001  aws_s3_bucket.datasets
+         tests/fixtures/insecure/s3_bad.tf:11
+         S3 bucket 'datasets' looks AI/ML related (matched: datasets) and its
+         bucket policy allows Principal "*". Anyone on the internet can perform
+         the granted actions.
+         fix: Restrict the policy principal to specific roles or accounts and
+         add an aws_s3_bucket_public_access_block with all four protections
+         enabled.
+
+HIGH     IAM-001  aws_iam_role_policy_attachment.full_access
+         tests/fixtures/insecure/iam_bad.tf:12
+         Role 'agent_role' attaches AWS managed policy
+         'arn:aws:iam::aws:policy/AmazonBedrockFullAccess', which grants blanket
+         AI service access. The role is used by Lambda function(s) public_agent,
+         vpc_agent.
+```
+
+## Checks
+
+| ID | What it finds | Severity range |
+|----|---------------|----------------|
+| SMK-001 | SageMaker models with no `vpc_config`, so containers run on the managed network with direct internet egress | HIGH |
+| IAM-001 | Wildcard AI grants (`bedrock:*`, `sagemaker:*` on `Resource "*"`) in inline policies, customer managed policies, policy documents, or attached AWS `FullAccess` policies | HIGH |
+| S3-001 | AI-related buckets exposed by a public ACL or a `Principal "*"` policy, plus weakened or missing public access blocks | CRITICAL to LOW |
+| VPC-001 | Lambda functions calling Bedrock or SageMaker with no matching interface VPC endpoint in the project | MEDIUM to LOW |
+| VEC-001 | OpenSearch, pgvector-capable Postgres, and AI-named ElastiCache missing encryption or network isolation | CRITICAL to LOW |
+
+## Exit codes and CI
+
+`modelmoat scan` exits 1 when findings at or above `--fail-on` exist, and 0
+otherwise. The default is `HIGH`, so hygiene findings do not break builds.
+Exit code 2 means bad arguments.
+
+```yaml
+- name: Scan AI infrastructure
+  run: |
+    pip install modelmoat
+    modelmoat scan infra/ --fail-on HIGH
+```
+
+Tighten with `--fail-on MEDIUM` once your baseline is clean, or loosen to
+`CRITICAL` while you work through a backlog. `--min-severity` controls what gets
+printed and is separate from what fails the build, so you can see everything
+while only blocking on the serious findings.
+
+## How severity is decided
+
+CRITICAL means the configuration itself proves internet reachability with weak
+or absent authentication. A bucket policy granting `Principal "*"` qualifies. A
+SageMaker model outside a VPC does not, because invoking it still requires a
+SigV4-signed IAM request, and modelmoat says exactly that in the finding rather
+than claiming anyone with the URL can hit your model.
+
+HIGH covers missing encryption and permissions broad enough to reach any AI
+resource in the account. MEDIUM and LOW are hygiene: a missing public access
+block is LOW, since account defaults have blocked public access on new buckets
+since April 2023, and calling it CRITICAL would be wrong.
+
+## Design notes
+
+Values that come from variables or expressions are unknown, and modelmoat does
+not flag what it cannot prove. `storage_encrypted = var.encrypt_storage` produces
+no finding either way.
+
+Keyword matching is on whole tokens, never substrings. A bucket named
+`email-archive` does not match `ai`, and `html-assets` does not match `ml`. Both
+appear in the test suite as negative controls that must stay silent.
+
+The test suite has one rule above all others: the secure fixture must produce
+zero findings. A scanner that fires on correct infrastructure trains people to
+ignore it, so CI runs both directions on every push, requiring a clean pass on
+nine files of best-practice Terraform and a failing exit code on the insecure
+fixture.
+
+## Limitations
+
+modelmoat reads HCL statically. It does not evaluate modules, resolve variable
+files, expand `for_each`, or read remote state, so a security control defined in
+a module that this project only calls will not be seen. Coverage is AWS only
+today, and provider-specific vector databases like Pinecone and Weaviate are not
+yet checked.
+
+Static analysis cannot tell you whether a security group actually permits the
+traffic you fear, or whether an IAM permission is used. Treat findings as places
+to look, not verdicts.
+
+## Roadmap
+
+Pinecone and Weaviate providers, SARIF output for GitHub code scanning, Azure AI
+and Vertex AI resources, and a `--baseline` file for adopting the tool on an
+existing codebase without a wall of findings on day one.
+
+## Contributing
+
+False positive reports are as welcome as new checks and get the same priority.
+See CONTRIBUTING.md for the rules every check follows and SECURITY.md for
+reporting a vulnerability in the tool itself.
+
+## License
+
+Apache-2.0.