vulnly 1.0.0__tar.gz

vulnly-1.0.0/LICENSE

@@ -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.

vulnly-1.0.0/PKG-INFO

@@ -0,0 +1,441 @@
+Metadata-Version: 2.4
+Name: vulnly
+Version: 1.0.0
+Summary: Generate offline, self-contained HTML vulnerability reports from Cloudsmith, Trivy, Grype and Snyk scan output
+Author-email: Colin Moynes <colinmoynes@gmail.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/colinmoynes/Vulnly
+Project-URL: Issues, https://github.com/colinmoynes/Vulnly/issues
+Keywords: vulnerability,security,scanner,report,trivy,grype,cloudsmith,html
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: System Administrators
+Classifier: Intended Audience :: Information Technology
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+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: Topic :: Security
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0; extra == "dev"
+Dynamic: license-file
+
+<img src="https://raw.githubusercontent.com/colinmoynes/vulnly/main/assets/icons/vulnly-readme-banner.png" alt="Vulnly" width="800">
+
+Generate self-contained HTML vulnerability reports from Cloudsmith, Trivy, Grype and Snyk.
+Every report is a single file that opens with no network access.
+
+![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)
+![Python](https://img.shields.io/badge/python-3.10%2B-blue.svg)
+
+## Installation
+
+Install from PyPI (Currently in beta):
+
+```bash
+pip install vulnly
+```
+
+## Features
+
+- **Fully offline reports** — a single HTML file with fonts, charting library and logo embedded. No CDN, no web fonts, no outbound requests when opened, so reports work on airgapped hosts and keep working once archived
+- Supports multiple scanner sources: **Cloudsmith**, **Trivy**, **Grype**, and **Snyk** (auto-detected or via `--source` flag)
+- **Repository summary reports** — automatically detects Cloudsmith repo-level summaries and generates a dedicated overview report with package status breakdown, aggregate vulnerability counts, and per-package detail table
+- Dark and light colour themes via `--theme` flag, plus an in-report toggle so readers can switch without regenerating
+- Interactive doughnut charts showing severity or status distribution (Chart.js, bundled)
+- Severity stat cards (Total, Critical, High, Medium, Low, Unknown) and a count of findings that have a fix available
+- **Top affected packages** — a ranked breakdown showing where findings are concentrated, since one bad dependency usually dominates a scan
+- Auto-generated executive summary, with an alert that distinguishes urgent findings from routine ones and from a clean scan
+- Client-side search, severity filters and a fixable-only toggle, with sortable columns and pagination so large reports stay usable
+- **CSV export** of the current filtered view, safe to open in a spreadsheet
+- Automatic linking for CVE IDs (NVD) and GHSA IDs (GitHub Advisories)
+- Customisable logo — supply via `--logo`, embedded in the report as a data URI
+- Accepts input from a file or stdin (`-`), making it easy to pipe from other tools
+- Input validation with helpful warnings for malformed data
+- Zero external dependencies — uses only the Python standard library
+
+## Quick Start
+
+```bash
+vulnly sample_data.json
+```
+
+This reads `sample_data.json` and writes the report to `reports/` (the default output directory).
+
+### Specify the scanner source
+
+The tool auto-detects the input format, but you can be explicit:
+
+```bash
+vulnly scan.json --source trivy
+vulnly scan.json --source grype
+vulnly scan.json --source snyk
+vulnly scan.json --source cloudsmith
+```
+
+If `--source` is specified and the input doesn't match the expected format, the tool exits with a clear error message.
+
+### Repository summary reports
+
+Cloudsmith repo-level summary JSON is automatically detected and generates a dedicated repository overview report:
+
+```bash
+vulnly repo_summary.json
+```
+
+The output includes package status cards (vulnerable / no issues / not scanned), aggregate vulnerability severity breakdown, a status distribution chart, and a searchable/filterable package table.
+
+### Specify a custom output path
+
+```bash
+vulnly sample_data.json -o my_report.html
+```
+
+### Custom logo
+
+Use the `--logo` flag to supply a custom logo image. It will be embedded directly in the HTML report header as a base64 data URI:
+
+```bash
+vulnly sample_data.json --logo my-company-logo.png
+```
+
+**Logo requirements:**
+
+| Constraint | Limit |
+|---|---|
+| Max file size | 2 MB |
+| Max dimensions | 512 × 512 px |
+| Recommended size | 128 × 128 px to 256 × 256 px |
+| Supported formats | `.png`, `.jpg`, `.jpeg`, `.gif`, `.svg`, `.webp`, `.ico` |
+
+If a custom logo exceeds the file size or dimension limits, a warning is printed and the default Vulnly logo is used instead.
+
+If no `--logo` is provided, the built-in Vulnly logo is used.
+
+### Theme
+
+Choose the theme the report opens in — dark is the default:
+
+```bash
+vulnly sample_data.json --theme light
+vulnly sample_data.json --theme dark
+```
+
+Every report also carries both palettes, so readers can switch with the
+toggle in the report header regardless of which theme it was generated in.
+Their choice is remembered per browser.
+
+### Read from stdin
+
+Pipe JSON directly from another command:
+
+```bash
+cat scan_output.json | vulnly -
+```
+
+#### Cloudsmith CLI
+
+Pipe vulnerability scan results directly from the Cloudsmith CLI:
+
+```bash
+cloudsmith vulnerabilities WORKSPACE/REPO/PACKAGE_IDENTIFIER --output-format json | vulnly -
+```
+
+#### Trivy
+
+Scan an image with Trivy and pipe directly to Vulnly:
+
+```bash
+trivy image -f json nginx:latest | vulnly --source trivy -
+```
+
+#### Grype
+
+Scan an image with Grype and pipe directly to Vulnly:
+
+```bash
+grype nginx:latest -o json | vulnly --source grype -
+```
+
+#### Snyk
+
+Test a container image with Snyk and pipe directly to Vulnly:
+
+```bash
+snyk container test nginx:latest --json | vulnly --source snyk -
+```
+
+## Example report
+
+The scan summary — severity and fixable counts, the distribution chart, and an
+executive summary whose alert reflects whether anything is actually urgent:
+
+<img src="https://raw.githubusercontent.com/colinmoynes/vulnly/main/assets/readme/example.jpg" alt="Vulnly report summary: stat cards, severity distribution chart and executive summary">
+
+Further down, the findings themselves — where they are concentrated, then a
+sortable table with search, severity and fixable filters, and CSV export:
+
+<img src="https://raw.githubusercontent.com/colinmoynes/vulnly/main/assets/readme/example2.jpg" alt="Vulnly findings: top affected packages breakdown and the filterable vulnerability table">
+
+## Usage
+
+```
+usage: vulnly [-h] [-v] [-o OUTPUT] [--logo LOGO]
+              [--theme {dark,light}] [--source SOURCE]
+              input
+
+Generate an HTML vulnerability report from a JSON input file.
+
+positional arguments:
+  input                 Path to the JSON file containing vulnerability
+                        data (use '-' for stdin)
+
+options:
+  -h, --help            show this help message and exit
+  -v, --version         show program's version number and exit
+  -o, --output OUTPUT   Output HTML file path (default: auto-generated
+                        from package metadata)
+  --logo LOGO           Path to a custom logo image (embedded in the
+                        report as a data URI)
+  --theme {dark,light}  Report colour theme (default: dark)
+  --source SOURCE       Scanner source format: cloudsmith, grype, snyk,
+                        trivy (auto-detected if omitted)
+```
+
+### Environment variables
+
+| Variable | Effect |
+| --- | --- |
+| `VULNLY_NO_UPDATE_CHECK` | Set to any value to skip the PyPI version check. |
+
+The version check is skipped automatically when stderr is not a terminal, so
+it makes no network request in CI or when output is piped.
+
+## Offline reports
+
+A generated report is a single HTML file that makes **no network requests when
+opened**. Everything it needs is embedded:
+
+| Asset | Source | Licence |
+| --- | --- | --- |
+| Charting | Chart.js 4.4.0, bundled and inlined | MIT |
+| Typography | Inter, variable font covering weights 400–800 | SIL OFL 1.1 |
+| Logo | Embedded as a data URI | — |
+
+This means reports render identically on airgapped hosts and in restricted
+browser environments, and keep rendering years later when a CDN URL would have
+moved. It also means opening a report tells no third party that you did.
+
+CVE and GHSA identifiers still link out to NVD and GitHub Advisories, but those
+are ordinary links — nothing is fetched unless the reader clicks one.
+
+The generator itself contacts the network only for its PyPI version check,
+which can be disabled with `VULNLY_NO_UPDATE_CHECK` as described above.
+
+## Input JSON Format
+
+The generator accepts **multiple input formats** — it auto-detects which one you provide, or you can specify explicitly with `--source`.
+
+### 1. Cloudsmith package format
+
+Pass raw JSON output from the Cloudsmith CLI. The tool extracts namespace, repository, package metadata, scan target, and all vulnerabilities automatically.
+
+The expected structure has a top-level `data` object containing `package`, `scans`, etc.:
+
+```json
+{
+    "data": {
+        "created_at": "2025-06-09T08:39:20.441354Z",
+        "identifier": "TZR5N4HaO7nTclhz",
+        "package": {
+            "name": "log4j",
+            "url": "https://example.com/packages/my-org/java/wAoMy00juV6N/",
+            "version": "28a05d8e..."
+        },
+        "scans": [
+            {
+                "target": "Java",
+                "type": "jar",
+                "results": [
+                    {
+                        "vulnerability_id": "CVE-2021-45046",
+                        "severity": "Critical",
+                        "title": "DoS in log4j 2.x...",
+                        "package_name": "org.apache.logging.log4j:log4j-core",
+                        "affected_version": { "version": "2.8.1" },
+                        "fixed_version": { "version": "2.16.0, 2.12.2" },
+                        "cvss_scores": null
+                    }
+                ]
+            }
+        ]
+    }
+}
+```
+
+### 2. Cloudsmith repository summary format
+
+Pass the repo-level summary JSON from Cloudsmith. This is auto-detected and produces a repository overview report instead of a per-package vulnerability report:
+
+```json
+{
+    "data": {
+        "owner": "my-org",
+        "packages": [
+            {
+                "package": "cloudsmith.io/jdk:9ea72e62...",
+                "slug_perm": "XXVmdsZn7OEh",
+                "status": "vulnerable",
+                "vulnerabilities": {
+                    "critical": 0,
+                    "high": 0,
+                    "low": 1,
+                    "medium": 2,
+                    "unknown": 0
+                }
+            },
+            {
+                "package": "cloudsmith.io/jdk:5659dd01...",
+                "slug_perm": "Ft30zuSymLol",
+                "status": "no_issues_found",
+                "vulnerabilities": {
+                    "critical": 0,
+                    "high": 0,
+                    "low": 0,
+                    "medium": 0,
+                    "unknown": 0
+                }
+            }
+        ],
+        "repository": "chainguard"
+    }
+}
+```
+
+The report includes status cards (vulnerable, no issues, not scanned), aggregate severity totals, a doughnut chart of package status, and a filterable package table.
+
+Package status values: `vulnerable`, `no_issues_found`, `no_scan`.
+
+### 3. Trivy format
+
+Pass Trivy's JSON output (`trivy image -f json`). The tool maps `ArtifactName`, `Results[].Vulnerabilities[]`, CVSS scores, and fix versions:
+
+```bash
+trivy image -f json nginx:latest > trivy-output.json
+vulnly trivy-output.json
+```
+
+### 4. Grype format
+
+Pass Grype's JSON output (`grype -o json`). The tool maps `matches[]`, artifact metadata, CVSS scores, and fix versions:
+
+```bash
+grype nginx:latest -o json > grype-output.json
+vulnly grype-output.json
+```
+
+### 5. Snyk format
+
+Pass Snyk's JSON output (`snyk container test --json`). The tool maps `vulnerabilities[]`, CVSS scores, CVE identifiers, and fix versions. Duplicate vulnerability paths are automatically deduplicated:
+
+```bash
+snyk container test nginx:latest --json > snyk-output.json
+vulnly snyk-output.json
+```
+
+### 6. Simplified format
+
+A flat JSON structure is also supported for custom integrations:
+
+```json
+{
+    "scan_date": "2026-03-13",
+    "repository": "my-org/production-repo",
+    "package_name": "my-application",
+    "package_version": "1.4.2",
+    "package_format": "Docker",
+    "scan_target": "debian 9.4",
+    "package_size": "~77.4 MB",
+    "scan_id": "TZR5N4HaO7nTclhz",
+    "vulnerabilities": [
+        {
+            "severity": "critical",
+            "identifier": "CVE-2026-1234",
+            "package": "openssl",
+            "affected_version": "1.1.1t",
+            "fixed_version": "1.1.1u",
+            "title": "Heap buffer overflow in OpenSSL",
+            "cvss": 9.8
+        }
+    ]
+}
+```
+
+#### Top-level fields
+
+| Field | Required | Description |
+|---|---|---|
+| `scan_date` | Yes | Date the scan was performed (`YYYY-MM-DD`) |
+| `repository` | Yes | Namespace/repository path (e.g. `my-org/production-repo`) |
+| `package_name` | Yes | Name of the scanned package |
+| `package_version` | Yes | Version of the scanned package |
+| `package_format` | No | Package format (e.g. `Docker`, `Maven`). Defaults to `Unknown` |
+| `scan_target` | No | Scan target OS/platform (e.g. `debian 9.4`). Defaults to `Unknown` |
+| `package_size` | No | Human-readable package size (e.g. `~77.4 MB`). Defaults to `Unknown` |
+| `scan_id` | No | Unique scan identifier. Defaults to `N/A` |
+| `vulnerabilities` | Yes | Array of vulnerability objects |
+
+#### Vulnerability object fields
+
+| Field | Required | Description |
+|---|---|---|
+| `severity` | Yes | One of `critical`, `high`, `medium`, `low` (case-insensitive) |
+| `identifier` | Yes | CVE ID or other identifier (e.g. `GHSA-...`). CVE IDs are auto-linked to NVD; GHSA IDs are linked to GitHub Advisories |
+| `package` | Yes | Name of the affected dependency |
+| `affected_version` | No | The vulnerable version |
+| `fixed_version` | No | The version containing the fix, or `"N/A"` / omit if no fix is available |
+| `title` | No | Short description of the vulnerability. Auto-generated if omitted |
+| `cvss` | No | CVSS v3 score as a number (e.g. `9.8`). Displayed as `N/A` if omitted |
+
+## Requirements
+
+- Python 3.10+
+
+## Terminal Output
+
+The script prints a severity breakdown after generating the report:
+
+```
+Report generated: reports/nginx_latest_nginx_latest_a72860cb95fd_grype_vulnerability_report.html (3 vulnerabilities)
+  CRITICAL: 1  MEDIUM: 1  LOW: 1
+```
+
+A clean scan says so explicitly:
+
+```
+Report generated: reports/chainguard_nginx_latest_..._trivy_vulnerability_report.html (0 vulnerabilities)
+  No vulnerabilities found.
+```
+
+When no `-o` is specified, reports are saved to the `reports/` subfolder. This directory is git-ignored by default.
+
+## Security
+
+Vulnly treats scanner output as untrusted: advisory titles and package names
+come from vulnerability feeds, and reports are shared and archived. Generated
+reports load nothing from the network, scanner text is never rendered as
+markup, and CSV exports are inert in a spreadsheet.
+
+To report a vulnerability in Vulnly itself, see [SECURITY.md](SECURITY.md).
+
+## License
+
+This project is licensed under the Apache License 2.0 — see the [LICENSE](LICENSE) file for details.