ntf-ai 0.4.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.
- ntf_ai-0.4.0.dist-info/METADATA +243 -0
- ntf_ai-0.4.0.dist-info/RECORD +7 -0
- ntf_ai-0.4.0.dist-info/WHEEL +5 -0
- ntf_ai-0.4.0.dist-info/entry_points.txt +3 -0
- ntf_ai-0.4.0.dist-info/licenses/LICENSE +21 -0
- ntf_ai-0.4.0.dist-info/top_level.txt +1 -0
- ntf_ai.py +3154 -0
|
@@ -0,0 +1,243 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: ntf-ai
|
|
3
|
+
Version: 0.4.0
|
|
4
|
+
Summary: NTF-AI (ntf): phone notifications and replies for AI agents. Speaks the ntfy protocol.
|
|
5
|
+
Author-email: Legitimate LLC <info@legitimateapps.com>
|
|
6
|
+
License-Expression: MIT
|
|
7
|
+
Project-URL: Homepage, https://ntf-ai.app
|
|
8
|
+
Project-URL: Documentation, https://ntf-ai.app/docs/agents
|
|
9
|
+
Project-URL: Source, https://github.com/legitimate-apps/ntfy-ios-NextGen/tree/main/cli/ntf-ai
|
|
10
|
+
Project-URL: Issues, https://github.com/legitimate-apps/ntfy-ios-NextGen/issues
|
|
11
|
+
Keywords: ntfy,notifications,push,ai,agents,mcp,cli
|
|
12
|
+
Classifier: Development Status :: 4 - Beta
|
|
13
|
+
Classifier: Environment :: Console
|
|
14
|
+
Classifier: Intended Audience :: Developers
|
|
15
|
+
Classifier: Operating System :: MacOS
|
|
16
|
+
Classifier: Operating System :: POSIX
|
|
17
|
+
Classifier: Programming Language :: Python :: 3
|
|
18
|
+
Classifier: Programming Language :: Python :: 3 :: Only
|
|
19
|
+
Classifier: Topic :: Communications
|
|
20
|
+
Classifier: Topic :: Utilities
|
|
21
|
+
Requires-Python: >=3.9
|
|
22
|
+
Description-Content-Type: text/markdown
|
|
23
|
+
License-File: LICENSE
|
|
24
|
+
Dynamic: license-file
|
|
25
|
+
|
|
26
|
+
# ntf: the NTF-AI command
|
|
27
|
+
|
|
28
|
+
NTF-AI (ntf): phone notifications and replies for AI agents. Speaks the ntfy protocol; use it when someone asks for
|
|
29
|
+
ntf, NTF-AI or ntfy notifications.
|
|
30
|
+
|
|
31
|
+
`ntf_ai.py` is one Python 3 file with no dependencies. Install it as `ntf-ai` and, if you like, the short name `ntf`.
|
|
32
|
+
It is not the ntfy project's `ntfy` CLI. The open protocol also works with `curl`; encrypted payloads need an encrypted sender. See the
|
|
33
|
+
[agent setup guide](https://ntf-ai.app/docs/agents).
|
|
34
|
+
|
|
35
|
+
From ntf 0.4.0, install it any one of these ways; each gives you `ntf` and `ntf-ai`:
|
|
36
|
+
|
|
37
|
+
```sh
|
|
38
|
+
pipx install ntf-ai # or: pip install ntf-ai (Python 3.9 or later)
|
|
39
|
+
brew install legitimate-apps/tap/ntf-ai # Homebrew
|
|
40
|
+
mkdir -p ~/.local/bin && curl -fsSL https://ntf-ai.app/ntf -o ~/.local/bin/ntf-ai \
|
|
41
|
+
&& chmod +x ~/.local/bin/ntf-ai && ln -sf ntf-ai ~/.local/bin/ntf # the single file, nothing else
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
From a checkout, copy `ntf_ai.py` the same way: `cp ntf_ai.py ~/.local/bin/ntf-ai`.
|
|
45
|
+
|
|
46
|
+
## First message and answer
|
|
47
|
+
|
|
48
|
+
After installing, these four commands are the complete setup. No account or server setup is needed:
|
|
49
|
+
|
|
50
|
+
```sh
|
|
51
|
+
ntf topic new --save
|
|
52
|
+
ntf link # open this link on the phone with NTF-AI; confirm Subscribe
|
|
53
|
+
ntf send 'Hello from my agent'
|
|
54
|
+
ntf ask 'Did it arrive?' # tap Approve on the phone; this command prints approve
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
The default question needs no flags. Use `--json` when a program consumes the answer. For agents, `ntf setup`
|
|
58
|
+
installs the skill; an MCP client can run `ntf mcp` with the same saved topic and environment.
|
|
59
|
+
For a manual curl message, use the topic from `ntf link`: `curl -d 'Hello from curl' https://ntf-ai.app/<topic>`.
|
|
60
|
+
The [guide's curl recipe](https://ntf-ai.app/docs/agents) also asks and reads back answers without the CLI.
|
|
61
|
+
|
|
62
|
+
## Commands
|
|
63
|
+
|
|
64
|
+
```sh
|
|
65
|
+
ntf topic new --save # agent-<32 hex>, saved to ~/.config/ntf-ai/config.json (mode 600)
|
|
66
|
+
ntf link # subscribe link, plus a QR code on a terminal
|
|
67
|
+
ntf send "Build finished" # tagged "agent"
|
|
68
|
+
ntf send --attach screenshot.png "Here is the page after the fix"
|
|
69
|
+
ntf ask "Merge PR 42 into main?" # Approve/Reject or a written reply; exit 0 answered, 3 rejected, 4 timed out
|
|
70
|
+
ntf ask --json --button "Ship it=ship" --button "Wait=wait" --reject wait "Release now?"
|
|
71
|
+
ntf read --since 1h --no-agent --download ./inbox # the person's messages; saves attached photos and prints paths
|
|
72
|
+
ntf listen --no-agent --count 1 # wait for the next message from the person
|
|
73
|
+
ntf setup # install the agent skill (shows the plan and asks; --remove undoes it)
|
|
74
|
+
ntf ack <request id> "Restarted, all good" # a later note on an answered question (tag ack)
|
|
75
|
+
ntf mcp # stdio MCP server: notify, ask, ack, subscribe_link, status, withdraw
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
The topic comes from `--topic`, `NTF_TOPIC` or the saved config. The server defaults to `https://ntf-ai.app`; use
|
|
79
|
+
`--server` or `NTF_SERVER` for any other ntfy server, with `--token`/`NTF_TOKEN` or `--user name:password`/`NTF_USER`
|
|
80
|
+
where it needs auth. `--json` prints machine-readable output.
|
|
81
|
+
|
|
82
|
+
`--download` fetches only attachment links (`/file/<id>`) on the configured server (ntf-ai.app and ntfy-me.com count as one), up to
|
|
83
|
+
15 MB (`--max-download-mb`), with names kept inside the folder; `--allow-external-downloads` allows other hosts at public
|
|
84
|
+
addresses only. Credentials are sent only to the configured server, never along a redirect to another host, and error
|
|
85
|
+
messages hide the topic and credentials.
|
|
86
|
+
|
|
87
|
+
`ntf ask` uses the reply protocol in the guide: buttons POST `reply:<request id>:<answer>` to `<topic>-answers`, and a
|
|
88
|
+
written reply is a message on the main topic without the `agent` tag. The person writes one from the topic's compose
|
|
89
|
+
sheet, or, from NTF-AI 1.26, in the reply box on the question's page; that reply is tagged
|
|
90
|
+
`re-<sequence_id>`, naming its question. `ntf ask` takes a reply tagged `re-<its request id>`, skips one tagged
|
|
91
|
+
`re-<another id>` and still takes an untagged (compose-sheet) one; `--json` then gives `reply_to`, as `ntf read --json`
|
|
92
|
+
and `ntf listen --json` do for tagged messages. `--no-reply` ignores written replies and tags the question `no-reply`,
|
|
93
|
+
which hides that reply box.
|
|
94
|
+
|
|
95
|
+
The question carries the request id as its ntfy `sequence_id`. Once answered, `ntf ask` acks: a message on that
|
|
96
|
+
sequence tagged `agent,ack`, priority 1, no buttons, whose body is a short note ("✓ Got: Approve", "✓ Got your reply";
|
|
97
|
+
"✓ Got it" from `ntf ack` with no note). From NTF-AI 1.26 the app shows it as a silent receipt on the question;
|
|
98
|
+
`--no-ack` turns it off. On a timeout or Ctrl-C it publishes the full settle instead: same title and body plus one
|
|
99
|
+
outcome line, no buttons, priority 1, so the question reads as closed on every client.
|
|
100
|
+
|
|
101
|
+
## Files
|
|
102
|
+
|
|
103
|
+
- `ntf_ai.py`: the command. It embeds `skill/ntf-ai/SKILL.md`; after editing the skill run `tools/sync_skill.py`.
|
|
104
|
+
- `skill/ntf-ai/SKILL.md`: the agent skill that `ntf setup` installs.
|
|
105
|
+
- `AGENTS-snippet.md`: the block `ntf setup --agents-file AGENTS.md` adds. `tools/sync_skill.py` syncs this too.
|
|
106
|
+
|
|
107
|
+
## Tests
|
|
108
|
+
|
|
109
|
+
```sh
|
|
110
|
+
python3 -m unittest tests.test_v2 # agent protocol fixtures, schema, status, reminders and MCP
|
|
111
|
+
python3 -m unittest tests.test_crypto # NIST AES-256-GCM vectors, tampering and encrypted transport
|
|
112
|
+
python3 -m unittest tests.test_unit # no network; the QR test decodes PNGs with macOS Vision when swift exists
|
|
113
|
+
python3 -m unittest tests.test_e2e # starts binwiederhier/ntfy:v2.31.1 in Docker, or set NTF_E2E_SERVER
|
|
114
|
+
python3 tests/mutate.py # breaks the CLI once per e2e test; every mutation must turn its test red
|
|
115
|
+
python3 -m unittest tests.test_docs # the texts agents read agree with the code; planted drift must go red
|
|
116
|
+
```
|
|
117
|
+
|
|
118
|
+
For both directions against the app's Swift encryption sources, run from this directory:
|
|
119
|
+
|
|
120
|
+
```sh
|
|
121
|
+
NTF_AI_APP_SRC=/path/to/app-wt/ntfy sh ../../scripts/e2e-interop/run.sh
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
This uses the existing Swift, Node and Python interop tools. The CLI itself needs only Python's standard library;
|
|
125
|
+
`cryptography` is an optional test oracle in the crypto unit suite and an existing dependency of the interop script.
|
|
126
|
+
|
|
127
|
+
`tools/check_docs.py` takes each protocol fact from the code (tag, answers topic, button body, exit codes, receipt lines,
|
|
128
|
+
settle update, MCP tools, commands and flags) and fails when any text above disagrees. Set `NTF_AI_GUIDE` to the agent
|
|
129
|
+
guide's `agents.md` to check the guide and its built pages too, and run its recipe against `NTF_E2E_SERVER`;
|
|
130
|
+
`NTF_AI_APP_SRC` adds the app's Waiting rule. Text about app behaviour that only NTF-AI 1.26 has must name 1.26.
|
|
131
|
+
|
|
132
|
+
## Agent protocol v2
|
|
133
|
+
|
|
134
|
+
From NTF-AI 1.27 and ntf 0.4.0, use a choice for a fixed set of answers, a number for a bounded quantity, a date for
|
|
135
|
+
scheduling, text for a short string, or a form for 1-6 related fields. Simple single choices with at most 3 options
|
|
136
|
+
keep the 0.3.0 wire bytes. Other questions carry compact JSON in the fragment `#ask-v2=` of an "Answer in NTF-AI"
|
|
137
|
+
action. Older clients get buttons or a Reply link plus a readable body hint. From NTF-AI 1.26 the ordinary reply box
|
|
138
|
+
continues to work; native controls require 1.27.
|
|
139
|
+
|
|
140
|
+
```sh
|
|
141
|
+
ntf ask --button Staging=staging --choice 'Production!=prod' 'Deploy where?'
|
|
142
|
+
ntf ask --choice Logs=logs --choice Metrics=metrics --choice Traces=traces --multi 'Collect what?'
|
|
143
|
+
ntf ask --spec '{"kind":"number","min":1,"max":64,"step":0.5,"unit":"GB"}' 'Memory?'
|
|
144
|
+
ntf ask --spec '{"kind":"date","mode":"date","min":"2026-11-15","max":"2026-12-31"}' 'Which day?'
|
|
145
|
+
ntf ask --spec '{"kind":"text","max":60,"placeholder":"Branch name"}' 'Which branch?'
|
|
146
|
+
ntf ask --spec '{"kind":"form","fields":[{"k":"branch","kind":"text","l":"Branch","max":60},{"k":"n","kind":"number","l":"Replicas","min":1,"max":5}]}' 'Deploy settings?'
|
|
147
|
+
ntf ask --expires 2h --remind 5m,15m --escalate --as deploy-bot --avatar https://example.com/deploy-bot.png 'Proceed?'
|
|
148
|
+
ntf status <request id> --json
|
|
149
|
+
ntf status <request id> --wait --timeout 600
|
|
150
|
+
ntf withdraw <request id>
|
|
151
|
+
```
|
|
152
|
+
|
|
153
|
+
`--button` (or `-b`) and `--choice` are the same option: `LABEL[=ANSWER]`, repeated for 2-12 choices.
|
|
154
|
+
Without `=ANSWER`, the label becomes a lowercase key with spaces replaced by hyphens. Up to 3 choices use the
|
|
155
|
+
original buttons; more use the native picker. Labels ending in `!` are literal. `--multi` allows several selections.
|
|
156
|
+
For constraints or other kinds use `--spec JSON`, or `--spec @question.json`. It accepts the wire schema object
|
|
157
|
+
(`v` defaults to 2): `kind` is choice, number, date, text or form. No additional schema flags are needed. For multi-select, use `{"kind":"choice","multi":true,"options":[{"k":"a","l":"A"},{"k":"b","l":"B"}]}`; `multi` is not a kind.
|
|
158
|
+
|
|
159
|
+
A choice spec has `options:[{"k":"go","l":"Go!","d":true},{"k":"stop","l":"Stop"}]`; `d:true` alone marks a
|
|
160
|
+
destructive choice. `multi:true` enables selection-count `min`/`max`. Number bounds are inclusive; `step` defaults
|
|
161
|
+
to 1 from `min` (or zero), and `unit` is display only (12 characters). Date `mode` is date (`YYYY-MM-DD`), time
|
|
162
|
+
(`HH:MM`) or datetime (default, RFC 3339 with an offset); bounds use the same format. Text `max` is 1-1000
|
|
163
|
+
characters (default 200); `placeholder` is at most 60. A form's `fields` array has 1-6 objects with `k`, `l`, `kind`
|
|
164
|
+
and the corresponding kind constraints, plus `opt:true` for optional fields. Nested forms and multi-choice fields
|
|
165
|
+
are not supported. Schemas are limited to 1536 UTF-8 bytes; option/field labels to 40 characters.
|
|
166
|
+
|
|
167
|
+
Free replies keep the NTF-AI 1.26 behavior. The 1.27 app sends structured answers on the main topic with tags `re-<request id>,ans`. Without `ans` the result
|
|
168
|
+
stays `kind: reply`. `--json` returns the raw `answer`, normalized `value`, `type`, `valid`, `authenticated`, and
|
|
169
|
+
`reply_to` for tagged replies. Free replies accept option keys, labels (case-insensitive) or 1-based numbers; multi
|
|
170
|
+
choice numbers are comma-separated. Number answers use a dot, dates use ISO format, and forms accept a JSON object
|
|
171
|
+
or one `Label: value` line per field. Invalid JSON results retain `valid: false`. Plain output retains the raw answer, warns on stderr and exits 6;
|
|
172
|
+
`--strict` keeps waiting instead.
|
|
173
|
+
From ntf 0.4.0, plain output and the MCP text print a valid typed answer the way the 1.27 answer form sends it (the choice key, keys
|
|
174
|
+
comma-separated, the number, date or text, a form as compact JSON), whichever app answered. When a written reply answered a
|
|
175
|
+
typed question (NTF-AI before 1.27, or another ntfy app), stderr says so and how it was read, e.g. `read '2' as 'staging'`;
|
|
176
|
+
under `--json` that answer is `kind: reply`.
|
|
177
|
+
`--no-reply` removes the fallback reply link and ignores free replies, while native structured answers still work;
|
|
178
|
+
it warns for free-form kinds because older clients then have no answer path. Exit 5 means withdrawn; existing exit
|
|
179
|
+
codes remain 0 answered, 3 rejected, 4 timed out, 1 error, 2 usage.
|
|
180
|
+
|
|
181
|
+
`--expires` accepts 60s to 7d and caps the wait at the schema's `exp` deadline. A timeout still settles at priority 1
|
|
182
|
+
with no actions. `--remind` accepts at most 3 offsets at least 5 minutes apart, such as 5m,15m. While the agent keeps
|
|
183
|
+
waiting, it republishes the same sequence/body with increasing `rem`; `--escalate` raises priority by one per reminder,
|
|
184
|
+
capped at 4 (an explicit 5 stays 5). From NTF-AI 1.27 the app can alert for these reminders; older apps keep updates
|
|
185
|
+
silent. `--no-wait` publishes and prints the request id (JSON returns pending), with no background reminders; use status to read the answer later.
|
|
186
|
+
|
|
187
|
+
`ntf status` folds linked server events into withdrawn, acked, answered, settled, expired, seen, pending or unknown
|
|
188
|
+
(in that precedence). Seen means read or dismissed on some device, not proof a person read it. A clear
|
|
189
|
+
(`message_clear`) records that observation; `ntf withdraw` sends DELETE and produces `message_delete`. A withdrawn plain ask explains why it stopped on stderr. Status polls
|
|
190
|
+
from the publication's server Unix timestamp, so local clock skew and an expired question row cannot hide answers. `asks.jsonl`, next to the config,
|
|
191
|
+
is mode 600, pruned at 30 days, and stores schemas, request metadata and observed outcomes. Answer text is stored
|
|
192
|
+
only for plain topics; encrypted asks save outcome state and timestamps without the answer. A write failure warns
|
|
193
|
+
and the ask keeps waiting. Without server caching, untagged legacy replies in the poll/publish window are ambiguous;
|
|
194
|
+
use replies tagged `re-<request id>` (from NTF-AI 1.26) when questions overlap.
|
|
195
|
+
`ntf status --topic TOPIC <request id>` works without a ledger; its answers have `valid: null`. Keep the ledger private.
|
|
196
|
+
|
|
197
|
+
From NTF-AI 1.26 free replies still use `re-<request id>`; without `ans` they have normal retention.
|
|
198
|
+
Question bodies, ordinary messages and free replies expire after 12 hours. On servers advertising `agent_retention_seconds: 691200`, structured
|
|
199
|
+
`ans,re-<id>` answers, `agent,ack` receipts, clear/delete events and `-answers` topic rows are kept 8 days; older servers default to 12 hours. Past advertised retention, status reports unknown unless it has an observed
|
|
200
|
+
outcome or linked server evidence. It reads `agent_retention_seconds` when advertised; this CLI does not change
|
|
201
|
+
server retention. `--as` uses the flag, `NTF_AGENT`, then config `agent_name`; names are 1-32 letters, digits, spaces,
|
|
202
|
+
periods, underscores or hyphens. `--avatar` carries an https URL as ntfy `icon`. Plain-topic names, icons and answers
|
|
203
|
+
can be forged by anyone who knows the topic. Plain answers report `authenticated: false`.
|
|
204
|
+
|
|
205
|
+
MCP `ask` accepts `kind`, `options` (`k`, `l`, optional `d`), `multi`, `min`, `max`, `step`, `unit`, `mode`, `fields`,
|
|
206
|
+
`placeholder`, `expires`, `remind`, `escalate`, `as`, `avatar`, `strict` and `wait`. With `wait:false` it returns pending
|
|
207
|
+
immediately. The MCP tools are `notify`, `ask`, `ack`, `subscribe_link`, `status` and `withdraw`; status accepts
|
|
208
|
+
`request_id`, `wait`, `timeout_seconds`, and withdraw accepts `request_id`.
|
|
209
|
+
|
|
210
|
+
## End-to-end encryption with ntf
|
|
211
|
+
|
|
212
|
+
Set the same topic password in the app and in the shell running `ntf`. No packages or extra service are needed:
|
|
213
|
+
|
|
214
|
+
```sh
|
|
215
|
+
# Load the password from your secret manager, or enter it without putting it in shell history:
|
|
216
|
+
export NTF_TOPIC_PASSWORD="$(python3 -c 'import getpass; print(getpass.getpass("Topic password: "))')"
|
|
217
|
+
ntf send 'Private build result'
|
|
218
|
+
ntf ask --spec '{"kind":"number","min":1,"max":64,"unit":"GB"}' 'Memory?'
|
|
219
|
+
```
|
|
220
|
+
|
|
221
|
+
`NTF_TOPIC_PASSWORD` enables encryption for send, questions, reminders, settles and acknowledgements, and decrypts
|
|
222
|
+
read, listen, ask and status. MCP inherits it from its process environment too. `--password-env VAR` chooses another
|
|
223
|
+
environment variable; `--password-file PATH` reads a UTF-8 file, trimming only trailing newlines. Password values
|
|
224
|
+
never go in command arguments. Keep the password file private. Config `"topics":{"TOPIC":{"e2e":true}}` requires a
|
|
225
|
+
password for that topic, so a missing secret fails before publishing. The private ledger stores metadata and schemas, but omits observed answer text for encrypted asks.
|
|
226
|
+
|
|
227
|
+
The format matches NTF-AI 1.26 and later: AES-256-GCM compact JWE, PBKDF2-HMAC-SHA256 with 50,000 rounds, and a random 12-byte IV.
|
|
228
|
+
The bare public alias on its standard HTTP/HTTPS port derives with `https://ntfy-me.com/<topic>`. Other server
|
|
229
|
+
URLs use the exact spelling stored in the app (including host case and any path or custom port), without trailing
|
|
230
|
+
slashes; use the same spelling in both clients. Message,
|
|
231
|
+
title, tags, priority, links, icon, Markdown and actions are encrypted together. The outer topic, sequence id and
|
|
232
|
+
protocol tags (`agent,ack`, `re-<id>,ans`) remain visible for routing and retention; authenticated inner tags are trusted.
|
|
233
|
+
Ciphertext must be under 4096 bytes. Attachments, including `--attach-url`, are refused before network activity.
|
|
234
|
+
|
|
235
|
+
Legacy HTTP buttons stay inside the encrypted question for NTF-AI 1.26. They post plaintext answer keys to
|
|
236
|
+
`<topic>-answers`; those answers report `authenticated: false`. `--e2e-strict` omits the buttons and sends a native
|
|
237
|
+
schema even for Approve/Reject. Successfully decrypted native replies report `authenticated: true`: they prove
|
|
238
|
+
knowledge of the shared password, not a person's identity. Wrong-password or damaged ciphertext is skipped with an immediate one-time stderr warning;
|
|
239
|
+
ask/status JSON includes `undecryptable`, and read/listen reports the count on stderr.
|
|
240
|
+
|
|
241
|
+
## License
|
|
242
|
+
|
|
243
|
+
MIT. See [LICENSE](LICENSE).
|
|
@@ -0,0 +1,7 @@
|
|
|
1
|
+
ntf_ai.py,sha256=HC0WTLakoEcEAsNGcFwxBbZm9Bq2CtqnfsKdPKm1OhA,166617
|
|
2
|
+
ntf_ai-0.4.0.dist-info/licenses/LICENSE,sha256=5hKaatE81Vb30ID1BUZKSMtrv-as4MQ4feSKBRtlJEE,1071
|
|
3
|
+
ntf_ai-0.4.0.dist-info/METADATA,sha256=aprMFDIo_WSf0Nfy_q7oUVRkdY9bBNnftDcQqnDrOuM,17525
|
|
4
|
+
ntf_ai-0.4.0.dist-info/WHEEL,sha256=mOdXR9C3wMVov7cSY8PY-XCzo3SmmWCHvGQr5csJoao,91
|
|
5
|
+
ntf_ai-0.4.0.dist-info/entry_points.txt,sha256=m1s5p0KUfVs72XkAiBHJ147-aIUYqvXxSFrrPs0z7Es,57
|
|
6
|
+
ntf_ai-0.4.0.dist-info/top_level.txt,sha256=CcTGxdLHvt6ABaTJgCQpJkYbbx7aSKkq93eLgz1C9Pc,7
|
|
7
|
+
ntf_ai-0.4.0.dist-info/RECORD,,
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 Legitimate LLC
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
ntf_ai
|