remedify 0.8.0__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,246 @@
1
+ Metadata-Version: 2.4
2
+ Name: remedify
3
+ Version: 0.8.0
4
+ Summary: Turn vulnerability scan results into concrete, OS-specific remediation commands
5
+ Author: Keita Higaki
6
+ License: Apache-2.0
7
+ Project-URL: Homepage, https://github.com/higakikeita/remedify
8
+ Project-URL: Issues, https://github.com/higakikeita/remedify/issues
9
+ Keywords: security,vulnerability,remediation,trivy,patching
10
+ Classifier: Development Status :: 3 - Alpha
11
+ Classifier: Intended Audience :: System Administrators
12
+ Classifier: License :: OSI Approved :: Apache Software License
13
+ Classifier: Programming Language :: Python :: 3
14
+ Classifier: Topic :: Security
15
+ Requires-Python: >=3.9
16
+ Description-Content-Type: text/markdown
17
+ License-File: LICENSE
18
+ Dynamic: license-file
19
+
20
+ # remedify
21
+
22
+ [![CI](https://github.com/higakikeita/remedify/actions/workflows/ci.yml/badge.svg)](https://github.com/higakikeita/remedify/actions/workflows/ci.yml)
23
+ [![License: Apache-2.0](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE)
24
+ [![Python 3.9+](https://img.shields.io/badge/python-3.9%2B-blue.svg)](pyproject.toml)
25
+ [![Zero dependencies](https://img.shields.io/badge/dependencies-0-brightgreen.svg)](remedify.py)
26
+
27
+ > **copa patches container images. remedify tells you how to patch everything else.**
28
+
29
+ Vulnerability scanners are great at telling you *what* is vulnerable and *which version* fixes it. They are terrible at telling you *what command to run*. After triage, every team asks the same question: "So how exactly do I fix this on my OS?" — and the answer today is "go read the Ubuntu/RHEL/Amazon Linux docs."
30
+
31
+ **remedify** closes that last-mile gap. It takes vulnerability scan results (Trivy, Grype, or Sysdig — API, JSON, and CSV) and generates concrete, distro-aware remediation:
32
+
33
+ ```
34
+ $ trivy rootfs --format json -o scan.json /
35
+ $ remedify scan.json
36
+ ```
37
+
38
+ ```markdown
39
+ ## libssl3 `HIGH`
40
+ - Installed: `3.0.2-0ubuntu1.15` -> Fix: `3.0.2-0ubuntu1.18`
41
+ - CVEs: CVE-2024-5535, CVE-2024-6119
42
+ - **Vendor backport (Ubuntu)**: the fixed version is a distro backport — it will
43
+ not match the upstream version number. Trust the vendor advisory below.
44
+
45
+ apt-get install --only-upgrade libssl3=3.0.2-0ubuntu1.18
46
+
47
+ - ⚠️ Restart services that link against OpenSSL (nginx, sshd, etc.).
48
+ - Advisories: [Ubuntu USN](https://ubuntu.com/security/notices/USN-6986-1)
49
+ ```
50
+
51
+ ## Quick start
52
+
53
+ ```bash
54
+ git clone https://github.com/higakikeita/remedify && cd remedify
55
+ # optional: pip install . → installs the `remedify` command
56
+
57
+ # 1. From Trivy
58
+ trivy image --format json -o scan.json nginx:latest
59
+ python3 remedify.py scan.json # Markdown report
60
+ python3 remedify.py scan.json --format shell > fix.sh # reviewable fix script
61
+ python3 remedify.py scan.json --min-severity HIGH --format json # for CI/automation
62
+
63
+ # 2. Straight from the Sysdig VM API (needs a Secure API token)
64
+ export SYSDIG_API_TOKEN=<token>
65
+ python3 remedify.py --from-sysdig --api-url https://us2.app.sysdig.com
66
+ python3 remedify.py --from-sysdig --api-url ... --limit 20 # 20 workloads, one report
67
+
68
+ # 2b. From Grype
69
+ grype myapp:1.0 -o json | python3 remedify.py -
70
+
71
+ # 3. From a Sysdig vulnerability report CSV export
72
+ python3 remedify.py report.csv --os ubuntu:22.04
73
+ ```
74
+
75
+ No dependencies — any Python 3.9+ runs it as-is.
76
+
77
+ ## How does this relate to copa and Sysdig Sage?
78
+
79
+ Honest answer: they overlap, and each occupies a different spot.
80
+
81
+ [Copacetic](https://project-copacetic.github.io/copacetic/website/) directly patches **container images** (adds a patch layer, no rebuild). Sysdig Sage Remediation generates high-quality, AI-assisted remediation strategies for **container images inside the Sysdig UI** — including dependency bump commands and base-image advice.
82
+
83
+ | | copa | Sysdig Sage | remedify |
84
+ |---|---|---|---|
85
+ | Container images | ✅ patches directly | ✅ AI remediation strategies (UI) | ✅ deterministic plan |
86
+ | **Hosts / VMs / bare metal** | ❌ | ❓ (not yet, per docs) | ✅ per-distro commands |
87
+ | Backport explanation (fixed version ≠ upstream) | ❌ | ❌ | ✅ |
88
+ | Reboot / service-restart guidance | ❌ | ❌ | ✅ |
89
+ | Batch / CI / scriptable (all workloads at once) | ✅ per image | ❌ per-image UI action | ✅ one command, JSON/shell out |
90
+ | Deterministic output (same input → same plan, diffable) | ✅ | ❌ AI-generated | ✅ |
91
+ | Works without Sysdig (Trivy/Grype users) | ✅ | ❌ | ✅ |
92
+
93
+ Position: containers with a registry workflow → copa; interactive triage inside Sysdig → Sage; **hosts, automation pipelines, and scanner-agnostic remediation plans → remedify**.
94
+
95
+ ## Features
96
+
97
+ - **Inputs** (auto-detected): Trivy JSON (`trivy image|fs|rootfs --format json`), **Sysdig scan-result JSON** (sysdig-cli-scanner / VM API), **Grype JSON**, **Sysdig vulnerability report CSV exports** (header names matched flexibly — pass `--os ubuntu:22.04` if your export lacks an OS column), or **live from the Sysdig VM API** (`--from-sysdig --api-url https://us2.app.sysdig.com` with `SYSDIG_API_TOKEN`; validated against a live tenant)
98
+ - **Priority signals**: findings carry Sysdig runtime context — 🚨 CISA KEV (known exploited), public exploit available, and **package in use at runtime** — and steps are sorted by severity + these signals, so you fix what attackers can actually reach first
99
+ - **Application dependencies (lang-pkgs)**: Java/npm/pip/Go/Ruby/PHP/Rust/.NET findings get ecosystem-specific fix instructions (update pom.xml / `npm install pkg@ver` / etc. + rebuild) — the class of finding neither OS package managers nor copa can fix
100
+ - **Distro-aware commands**: apt (Ubuntu/Debian), dnf/yum (RHEL/Rocky/Alma/Amazon/Fedora), apk (Alpine), zypper (SUSE)
101
+ - **Consolidated steps**: binary packages from one source package (e.g. e2fsprogs + libcom-err2 + libext2fs2 + libss2) become **one** command, not four
102
+ - **"No fix available" section**: findings without a fixed version are reported with their vendor status (`affected`, `will_not_fix`, `end_of_life`) — never silently dropped
103
+ - **EOL awareness**: detects end-of-life distro versions and warns when fixes require ESM enrollment or an OS migration
104
+ - **Backport detection**: flags vendor backports (`~ubuntu`, `.el9`, `.amzn2`, `+esm`, `+deb`) and explains why the version won't match upstream
105
+ - **Operational hints**: kernel → reboot required; glibc → reboot recommended; OpenSSL → restart linked services
106
+ - **Advisory surfacing**: vendor sources first (USN, RHSA, ALAS, DSA), NVD as fallback, near-duplicates collapsed
107
+ - **Three output formats**: Markdown report, executable shell script, JSON
108
+ - **Zero dependencies**: single-file Python, stdlib only
109
+
110
+ ## What you get
111
+
112
+ **1. A prioritized Markdown report** — consolidated steps instead of per-package noise:
113
+
114
+ ```markdown
115
+ # Remediation plan: `prod-web-host (ubuntu 18.04)`
116
+
117
+ - **Remediation steps**: 1 (covering 4 packages)
118
+ - **No fix available**: 1 packages
119
+
120
+ > ⚠️ **EOL**: Ubuntu 18.04 standard repositories no longer receive security
121
+ > updates. Fixes for many CVEs require Ubuntu Pro (ESM).
122
+
123
+ ## e2fsprogs (+3 related packages) `MEDIUM`
124
+
125
+ - Packages: `e2fsprogs`, `libcom-err2`, `libext2fs2`, `libss2` (same source, one update)
126
+ - Installed: `1.44.1-1ubuntu1.1` -> Fix: `1.44.1-1ubuntu1.2`
127
+ - **Vendor backport (Ubuntu)**: fixed version won't match upstream — trust the advisory.
128
+
129
+ apt-get install --only-upgrade e2fsprogs=1.44.1-1ubuntu1.2 libcom-err2=1.44.1-1ubuntu1.2 ...
130
+
131
+ - Advisories: [Ubuntu USN](https://ubuntu.com/security/notices/USN-4142-1)
132
+
133
+ ## No fix available
134
+
135
+ - **bash** `LOW` (CVE-2019-18276) — No vendor fix released yet
136
+ ```
137
+
138
+ **2. A reviewable shell script** (`--format shell`) — commented, `set -euo pipefail`, reboot reminder at the end:
139
+
140
+ ```bash
141
+ #!/usr/bin/env bash
142
+ # Review before running. Run as root or with sudo.
143
+ apt-get update
144
+
145
+ # e2fsprogs, libcom-err2, ... 1.44.1-1ubuntu1.1 -> 1.44.1-1ubuntu1.2 [MEDIUM] CVE-2019-5094
146
+ # NOTE: Ubuntu vendor backport — version differs from upstream
147
+ apt-get install --only-upgrade e2fsprogs=1.44.1-1ubuntu1.2 ...
148
+ ```
149
+
150
+ **3. Machine-readable JSON** (`--format json`) — feed it to your ticketing system, chatbot, or AI agent.
151
+
152
+ ## Use from AI agents (MCP)
153
+
154
+ remedify ships an MCP server (`remedify_mcp.py`, zero dependencies) so AI
155
+ agents get **deterministic** remediation plans instead of generating their
156
+ own commands. Claude Desktop config:
157
+
158
+ ```json
159
+ "mcpServers": {
160
+ "remedify": {
161
+ "command": "python3",
162
+ "args": ["/path/to/remedify/remedify_mcp.py"],
163
+ "env": { "SYSDIG_API_TOKEN": "..." }
164
+ }
165
+ }
166
+ ```
167
+
168
+ Tools: `generate_remediation_plan` (paste or point to any supported scan
169
+ file) and `fetch_sysdig_plan` (live from the Sysdig VM API, with fleet
170
+ summary). The agent reasons and talks; remedify computes the plan — same
171
+ input, same output, every time.
172
+
173
+ ## CLI reference
174
+
175
+ | Option | Values | Default | Purpose |
176
+ |---|---|---|---|
177
+ | `--format` | `markdown` `shell` `json` | `markdown` | Output format |
178
+ | `--min-severity` | `LOW` `MEDIUM` `HIGH` `CRITICAL` | show all | Filter remediation steps (unfixed findings are **never** hidden) |
179
+ | `--input` | `auto` `trivy` `grype` `sysdig-csv` `sysdig-json` | `auto` | Input format |
180
+ | `--os` | e.g. `ubuntu:22.04` | from input | OS override for inputs lacking OS metadata |
181
+ | `--from-sysdig` | | | Fetch runtime results from Sysdig VM API |
182
+ | `--limit` | N | 1 | With `--from-sysdig`: N most recent workloads in one report |
183
+ | `--api-url` / `--result-id` / `--filter` | | | Sysdig API endpoint / specific result / filter |
184
+ | `--version` | | | Print version |
185
+
186
+ Input via file path or stdin (`-`).
187
+
188
+ ## Supported distros
189
+
190
+ | Family | Package manager | Backport detection | EOL detection |
191
+ |---|---|---|---|
192
+ | Ubuntu / Debian | `apt` | ✅ (`~ubuntu`, `+deb`, `+esm`) | ✅ (ESM guidance) |
193
+ | RHEL / Rocky / Alma / Oracle / Fedora | `dnf` | ✅ (`.el9`) | — |
194
+ | CentOS | `dnf` | ✅ | ✅ (migration guidance) |
195
+ | Amazon Linux | `yum` (AL2) / `dnf` | ✅ (`.amzn2`) | ✅ (AL1) |
196
+ | Alpine | `apk` | — | — |
197
+ | SUSE / openSUSE | `zypper` | — | — |
198
+ | Anything else | — | degrades gracefully: findings listed without commands | |
199
+
200
+ Try it with the bundled examples:
201
+
202
+ ```
203
+ python3 remedify.py examples/trivy-real-ubuntu1804.json # real Trivy output: grouping + EOL + no-fix
204
+ python3 remedify.py examples/trivy-rhel.json --min-severity HIGH
205
+ python3 remedify.py examples/trivy-amazon2.json # yum + ALAS advisories
206
+ python3 remedify.py examples/trivy-alpine.json # apk
207
+ python3 remedify.py examples/trivy-centos7-eol.json # EOL + will_not_fix / end_of_life
208
+ python3 remedify.py examples/sysdig-report.csv # Sysdig CSV export
209
+ python3 remedify.py examples/sysdig-scan-result.json # Sysdig scan JSON: OS + Java/npm (Spring4Shell)
210
+ python3 remedify.py examples/trivy-ubuntu.json --format shell > fix.sh
211
+ ```
212
+
213
+ ## Architecture
214
+
215
+ ```
216
+ scan results parser normalized generators renderers
217
+ ┌────────────┐ ┌───────────┐ ┌──────────────┐ ┌──────────────┐ ┌────────────┐
218
+ │ Trivy JSON │──▶│ trivy.py │──▶│ Finding │──▶│ apt / dnf / │──▶│ markdown │
219
+ │ Grype JSON │ │ (grype 🔜)│ │ pkg, │ │ apk / zypper │ │ shell │
220
+ │ Sysdig 🔜 │ │ │ │ fix ver, │ │ + backport │ │ json │
221
+ └────────────┘ └───────────┘ │ CVEs, refs │ │ + hints │ │ sarif 🔜 │
222
+ └──────────────┘ └──────────────┘ └────────────┘
223
+ ```
224
+
225
+ Each stage is pluggable: new scanners are parsers, new distros are generators, new outputs are renderers.
226
+
227
+ ## Roadmap
228
+
229
+ - **v0.2 — inputs**: Grype JSON, Sysdig vulnerability report CSV/JSON
230
+ - **v0.3 — enrichment**: query vendor security data (Ubuntu OVAL/USN API, Red Hat CSAF/errata API, ALAS) to add "not affected / needs-restart" precision beyond what the scanner reports
231
+ - **v0.4 — containers**: emit copa-compatible patch workflows for image findings; language packages (pip/npm) remediation
232
+ - **v0.5 — integration**: GitHub Action, `--format sarif`, Windows (KB articles / `winget`), MCP server so AI agents can call it
233
+ - **Rewrite in Go** once the interface stabilizes (single static binary, same ecosystem as copa/trivy)
234
+
235
+ ## Non-goals
236
+
237
+ - remedify does **not** apply patches. It generates the plan; a human (or your automation) executes it. Auto-apply is deliberately out of scope for v0.x.
238
+ - Not a scanner. Bring your own (Trivy/Grype/Sysdig).
239
+
240
+ ## Status
241
+
242
+ PoC / pre-alpha. Name provisional. Feedback and contributions welcome.
243
+
244
+ ## License
245
+
246
+ Apache-2.0 (proposed).
@@ -0,0 +1,8 @@
1
+ remedify.py,sha256=crAtrps7y5M3s6w0mjKH6--tiQmOlTmv-BcqkYIjxy4,54071
2
+ remedify_mcp.py,sha256=MF09LsMceI7ciFIkeVjXBWb43WGTTjScUfruzmMJTlc,7701
3
+ remedify-0.8.0.dist-info/licenses/LICENSE,sha256=9hH5ne5LwiRmuLMnxF2av7eghuQWwdQywxO21UgJKYQ,11348
4
+ remedify-0.8.0.dist-info/METADATA,sha256=lpgraI7cON2wZBp0gtD0PrjgwQ1-A99eeV3sYV1oZAk,12877
5
+ remedify-0.8.0.dist-info/WHEEL,sha256=K260EYznzXsJYBQGqmI8VTxEdiZYNvDZwW9cBh9-_MA,91
6
+ remedify-0.8.0.dist-info/entry_points.txt,sha256=iMPfNNbbvThEljSkuT-FX-tXSbfwC1mpr8AHxulwo0c,43
7
+ remedify-0.8.0.dist-info/top_level.txt,sha256=zcui23mU0peosJJViF4IT4bP1M_dlZUfAU-CHoBJC1Y,22
8
+ remedify-0.8.0.dist-info/RECORD,,
@@ -0,0 +1,5 @@
1
+ Wheel-Version: 1.0
2
+ Generator: setuptools (83.0.0)
3
+ Root-Is-Purelib: true
4
+ Tag: py3-none-any
5
+
@@ -0,0 +1,2 @@
1
+ [console_scripts]
2
+ remedify = remedify:main
@@ -0,0 +1,202 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this
152
+ License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright 2026 Keita Higaki
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
@@ -0,0 +1,2 @@
1
+ remedify
2
+ remedify_mcp