github-security-report 0.1.0__tar.gz

github_security_report-0.1.0/.gitignore

@@ -0,0 +1,66 @@
+# SPDX-License-Identifier: Apache-2.0
+# SPDX-FileCopyrightText: 2025 The Linux Foundation
+
+# Temporary and binary files
+*~
+*.py[cod]
+*.so
+*.cfg
+!.isort.cfg
+!setup.cfg
+*.orig
+*.log
+*.pot
+__pycache__/*
+.cache/*
+.*.swp
+*/.ipynb_checkpoints/*
+.DS_Store
+
+# Project files
+.ropeproject
+.project
+.pydevproject
+.settings
+.idea
+.vscode
+tags
+
+# Package files
+*.egg
+*.eggs/
+.installed.cfg
+*.egg-info
+
+# Unittest and coverage
+htmlcov/*
+.coverage
+.coverage.*
+.tox
+junit*.xml
+coverage.xml
+.pytest_cache/
+
+# Build and docs folder/files
+build/*
+dist/*
+sdist/*
+docs/api/*
+docs/_rst/*
+docs/_build/*
+cover/*
+MANIFEST
+
+# Per-project virtualenvs
+.venv*/
+.conda*/
+.python-version
+
+# Node
+node_modules/*
+
+# Phase 0 capability spike: captured live API data (review/scrub before use)
+phase0-output/
+
+# Generated by hatch-vcs at build time
+src/github_security_report/_version.py

github_security_report-0.1.0/LICENSE

@@ -0,0 +1 @@
+LICENSES/Apache-2.0.txt

github_security_report-0.1.0/LICENSES/Apache-2.0.txt

@@ -0,0 +1,201 @@
+                                 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.

github_security_report-0.1.0/PKG-INFO

@@ -0,0 +1,318 @@
+Metadata-Version: 2.4
+Name: github-security-report
+Version: 0.1.0
+Summary: Security and quality reporting across GitHub organisations
+Project-URL: Homepage, https://github.com/lfreleng-actions/github-security-report-action
+Project-URL: Repository, https://github.com/lfreleng-actions/github-security-report-action
+Project-URL: Issues, https://github.com/lfreleng-actions/github-security-report-action/issues
+Author-email: The Linux Foundation <mwatkins@linuxfoundation.org>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: codeql,dependabot,github,github-actions,linux-foundation,reporting,scorecard,secret-scanning,security,zizmor
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: httpx[http2]==0.28.1
+Requires-Dist: jinja2==3.1.6
+Requires-Dist: jsonschema==4.26.0
+Requires-Dist: pyyaml==6.0.3
+Requires-Dist: rich==15.0.0
+Requires-Dist: typer==0.26.7
+Provides-Extra: dev
+Requires-Dist: mypy==2.1.0; extra == 'dev'
+Requires-Dist: pytest-asyncio==1.4.0; extra == 'dev'
+Requires-Dist: pytest-cov==7.1.0; extra == 'dev'
+Requires-Dist: pytest==9.0.3; extra == 'dev'
+Requires-Dist: respx==0.23.1; extra == 'dev'
+Requires-Dist: ruff==0.15.16; extra == 'dev'
+Requires-Dist: syrupy==5.3.2; extra == 'dev'
+Requires-Dist: types-jsonschema==4.26.0.20260518; extra == 'dev'
+Requires-Dist: types-pyyaml==6.0.12.20250915; extra == 'dev'
+Description-Content-Type: text/markdown
+
+<!--
+# SPDX-License-Identifier: Apache-2.0
+# SPDX-FileCopyrightText: 2026 The Linux Foundation
+-->
+
+# 🔐 GitHub Security Report
+
+<!-- prettier-ignore-start -->
+<!-- markdownlint-disable-next-line MD013 -->
+[![Linux Foundation](https://img.shields.io/badge/Linux-Foundation-blue)](https://linuxfoundation.org/) [![Source Code](https://img.shields.io/badge/GitHub-100000?logo=github&logoColor=white&color=blue)](https://github.com/lfreleng-actions/github-security-report-action) [![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
+<!-- prettier-ignore-end -->
+
+> Security and quality **reporting** (not scanning) across GitHub
+> organisations. Aggregates existing signals — CodeQL, OpenSSF Scorecard,
+> zizmor, Dependabot, and secret scanning — and ranks the worst offenders so
+> remediation effort goes where it is needed.
+
+## 🗒️ Published reports
+
+<https://lfreleng-actions.github.io/github-security-report-action/>
+
+## What it does
+
+For each in-scope repository, every signal is classified into one of four
+states and rendered worst-first:
+
+- **Offenders** — enabled with open findings (a ranked table row).
+- **Clean** — enabled with zero findings (a count beneath the table).
+- **Not enabled** — supported but switched off (a nag list prompting you to
+  enable it).
+- **Unknown** — indeterminate (insufficient permission), footnoted separately.
+
+The single GitHub code-scanning feed is partitioned by `tool.name` into CodeQL,
+Scorecard, and zizmor; Scorecard prefers the external aggregate score and falls
+back to code-scanning findings. See [`docs/BRIEF.md`](docs/BRIEF.md) and
+[`docs/phase0-findings.md`](docs/phase0-findings.md) for the full design and the
+API research it is built on.
+
+Two further sections report **configuration posture** and **freshness** as plain
+tables (org mode):
+
+- **Dependabot** — three tables: repositories with vulnerability **alerts not
+  enabled**, repositories with **security updates not enabled**, and ecosystems
+  with no update `cooldown` configured (mandatory; any value passes).
+- **Releases / Tagging** — repositories overdue a release or tag, ranked by a
+  hidden compound staleness score. Repositories younger than
+  `release_min_age_days` (default 28; `0` includes all) and those in
+  `releases_exclude` are omitted.
+
+## Operating modes
+
+| Mode | Token | Scope | Output |
+| ---- | ----- | ----- | ------ |
+| `org` | fine-grained PAT (single org) or classic PAT (multiple orgs) | one or more organisations | GitHub Pages + Slack + terminal |
+| `repo` | `GITHUB_TOKEN` | the current repository only | job summary + outputs + optional PR gate |
+
+`scope: auto` resolves to org mode when configuration is supplied, otherwise
+repo mode for the detected repository. The ephemeral `GITHUB_TOKEN` cannot read
+org-wide security data, so org mode requires a PAT — see
+[Token permissions](#token-permissions) for the exact scopes.
+
+## Token permissions
+
+Repo mode needs nothing beyond the workflow's ephemeral `GITHUB_TOKEN`. Org mode
+needs a Personal Access Token; choose **one** of the two options below depending
+on how many organisations the report covers.
+
+All required access is **read-only**. The tool degrades any read it is not
+permitted to make to an "unknown" status rather than reporting a repository as
+clean, so an under-scoped token surfaces as unknowns in the report instead of
+silently wrong results — start minimal and widen if you see unknowns.
+
+### Single organisation — fine-grained PAT
+
+A fine-grained PAT is bound to one resource owner, so it works for a report
+covering a **single** organisation. Create it with **Resource owner** set to the
+organisation and **Repository access** set to *All repositories*, then grant:
+
+**Repository permissions** (all Read-only):
+
+| Permission | Used for |
+| ---------- | -------- |
+| Metadata | Mandatory baseline; listing organisation repositories |
+| Contents | `.github/dependabot.yml`, latest release, and tag dates |
+| Dependabot alerts | Open Dependabot vulnerability alerts |
+| Code scanning alerts | CodeQL / Scorecard / zizmor findings |
+| Secret scanning alerts | Open secret-scanning alerts |
+| Administration | Dependabot enablement + security-updates status, and effective branch rules |
+
+**Organization permissions** (Read-only):
+
+| Permission | Used for |
+| ---------- | -------- |
+| Administration | Organisation rulesets (detect tools enabled via a required workflow) |
+
+> A fine-grained token cannot span organisations. For a report covering more
+> than one org, use a classic PAT (below).
+
+### Multiple organisations — classic PAT
+
+A classic PAT is authorised across every organisation its creator can access
+(subject to SSO authorisation), so a single token can report on **multiple**
+organisations. Grant these scopes:
+
+| Scope | Used for |
+| ----- | -------- |
+| `repo` | Repository data, including private repositories |
+| `security_events` | Code scanning, secret scanning, and Dependabot alerts (org-bulk and per-repo) |
+| `read:org` | Listing organisation repositories and reading organisation rulesets |
+
+> For organisations that enforce SSO, the PAT must be **SSO-authorised** for
+> each target organisation, or the org-level endpoints return `403` (reported as
+> unknown). Store the token as a secret (e.g. `SECURITY_REPORT_PAT`) and
+> reference it by env-var name via `token_env`; never embed it in the config.
+
+## Usage
+
+### Org mode (scheduled report)
+
+```yaml
+- name: "Security report"
+  id: report
+  uses: lfreleng-actions/github-security-report-action@v0.1.0
+  with:
+    scope: "org"
+    config: "${{ secrets.GSR_CONFIG || vars.GSR_CONFIG }}"
+    token: "${{ secrets.SECURITY_REPORT_PAT }}"
+    output_dir: "site"
+    pages_url: "https://lfreleng-actions.github.io/github-security-report-action/"
+```
+
+A ready-to-use scheduled workflow lives in
+[`.github/workflows/reporting.yaml`](.github/workflows/reporting.yaml): it runs
+daily at 09:00 UTC, publishes to GitHub Pages every day, and posts a Slack
+digest only on the configured `report_day` (default Tuesday).
+
+### Repo mode (PR gate)
+
+```yaml
+- name: "Security report"
+  uses: lfreleng-actions/github-security-report-action@v0.1.0
+  with:
+    scope: "repo"
+    token: "${{ github.token }}"
+    fail_threshold: "high"  # fail the job on any open high/critical finding
+  # requires: permissions: { security-events: read }
+```
+
+## Configuration
+
+Configuration is JSON, supplied as a plain `vars.` entry or base64-encoded in a
+`secrets.` entry (base64 only to stop JSON braces tripping GitHub's log
+redaction — it is encoding, not encryption). Tokens are referenced by
+environment-variable name, never embedded.
+
+```json
+{
+  "slack": { "channel": "releng-scm", "report_day": "tuesday" },
+  "report": {
+    "top_n": 10,
+    "top_n_report": 10,
+    "top_n_cli": 10,
+    "top_n_slack": 10,
+    "include_archived": false,
+    "include_test": false,
+    "release_min_age_days": 28
+  },
+  "organizations": [
+    {
+      "name": "lfreleng-actions",
+      "token_env": "GITHUB_TOKEN",
+      "exclude": ["actions-template"],
+      "releases_exclude": ["internal-only-repo"]
+    }
+  ]
+}
+```
+
+`report_day` accepts a single weekday, a list of weekdays, `"never"`, or
+`"always"`.
+
+`top_n` controls how many offenders are shown per signal. It is the shared
+default for all three outputs; set any of `top_n_report` (GitHub Pages),
+`top_n_cli` (terminal), or `top_n_slack` (Slack digest) to override an
+individual output. Each can also be set at the CLI with `--top-n`,
+`--top-n-report`, `--top-n-cli`, and `--top-n-slack`.
+
+`report.release_min_age_days` (default `28`, `0` = include all) and the per-org
+`releases_exclude` tune the Releases / Tagging section; they can be overridden
+locally with `--release-min-age-days` and the repeatable `--releases-exclude`.
+
+The per-org `exclude` list removes repositories from analysis entirely; they are
+reported as **excluded** (distinct from "not enabled"), so an intentional
+exclusion is visible rather than silently dropped.
+
+`slack.channel` is optional. The action's `slack_channel` input (wired to the
+`SLACK_CHANNEL_ID` variable in `reporting.yaml`) overrides it, so the channel
+can live as an org/repo variable rather than in the config JSON. It must be the
+channel **ID** (`C0…`), not the name.
+
+### Config file location
+
+For local use you can drop the same JSON at a conventional per-user path and run
+with no flags — it is picked up automatically when no `--config`,
+`--config-data`, or `--org` is given (instead of erroring):
+
+```text
+$XDG_CONFIG_HOME/github-security-report/config.json
+# or, when XDG_CONFIG_HOME is unset:
+~/.config/github-security-report/config.json
+```
+
+An explicit `--config`, `--config-data`, or `--org` always takes precedence, and
+the action itself never reads this path (it is supplied configuration directly).
+Secrets stay out of the file: reference the token by environment-variable name
+via `token_env` (e.g. `SECURITY_REPORT_PAT`, exported in your shell or sourced
+from a secrets file) — the channel ID is the only Slack value the file holds,
+and the Slack **bot token** is consumed by the workflow, not the CLI.
+
+## Inputs
+
+<!-- markdownlint-disable MD013 -->
+
+| Name | Required | Default | Description |
+| ---- | -------- | ------- | ----------- |
+| `scope` | No | `auto` | `auto`, `org`, or `repo` |
+| `config` | No | — | JSON config (raw or base64) |
+| `org` | No | — | Single organisation (shorthand for org mode) |
+| `repo` | No | detected | `owner/name` for repo mode |
+| `token` | No | `${{ github.token }}` | PAT (org mode) or `GITHUB_TOKEN` (repo mode) |
+| `token_env` | No | `GITHUB_TOKEN` | Env var name the tool reads the token from |
+| `output_dir` | No | — | Directory for Pages output (org mode) |
+| `pages_url` | No | — | Published Pages URL (used in the Slack link) |
+| `slack_channel` | No | — | Slack channel ID; overrides the config `slack.channel` (e.g. the `SLACK_CHANNEL_ID` variable) |
+| `top_n` | No | `10` | Offenders per signal across all outputs (shared default) |
+| `top_n_report` | No | — | Offenders per signal in the GitHub Pages output (overrides `top_n`) |
+| `top_n_cli` | No | — | Offenders per signal in the terminal output (overrides `top_n`) |
+| `top_n_slack` | No | — | Offenders per signal in the Slack digest (overrides `top_n`) |
+| `fail_threshold` | No | `none` | `none`/`low`/`medium`/`high`/`critical`/`any` (repo mode) |
+| `force_notify` | No | `false` | Post to Slack regardless of `report_day` |
+| `tool_version` | No | `0.1.0` | Published PyPI version (ignored on pull requests) |
+| `use_local_source` | No | `false` | Run from the checked-out source instead of PyPI (for testing unreleased code from any event) |
+
+<!-- markdownlint-enable MD013 -->
+
+## Outputs
+
+| Name | Description |
+| ---- | ----------- |
+| `should_notify` | Whether today is a Slack notification day |
+| `slack_payload` | Prebuilt Slack `chat.postMessage` payload (JSON) |
+| `failed` | Whether the repo-mode fail threshold was met |
+
+## Running locally
+
+The tool is published to PyPI and runs with `uvx`. Inside a Git checkout with a
+`GITHUB_TOKEN` exported, it auto-detects the repository (preferring the
+`upstream` remote, then `origin`) and prints a Rich table report:
+
+```bash
+export GITHUB_TOKEN=ghp_your_token
+uvx github-security-report report
+
+# Or org mode locally with a PAT:
+uvx github-security-report report --org lfreleng-actions
+```
+
+## Development
+
+```bash
+uv sync --extra dev
+uv run pytest
+uv run ruff check src/ tests/
+```