web-cortex-framework 0.3.0__cp313-cp313-win_amd64.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.
- web_cortex_framework-0.3.0.dist-info/METADATA +390 -0
- web_cortex_framework-0.3.0.dist-info/RECORD +13 -0
- web_cortex_framework-0.3.0.dist-info/WHEEL +4 -0
- web_cortex_framework-0.3.0.dist-info/entry_points.txt +2 -0
- web_cortex_framework-0.3.0.dist-info/licenses/LICENSE +202 -0
- web_cortex_framework-0.3.0.dist-info/sboms/webcortex-py.cyclonedx.json +10024 -0
- webcortex/__init__.py +30 -0
- webcortex/_bridge.py +362 -0
- webcortex/_core.cp313-win_amd64.pyd +0 -0
- webcortex/app.py +1100 -0
- webcortex/cli.py +262 -0
- webcortex/schema.py +204 -0
- webcortex/starters.py +472 -0
|
@@ -0,0 +1,390 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: web-cortex-framework
|
|
3
|
+
Version: 0.3.0
|
|
4
|
+
Classifier: Development Status :: 3 - Alpha
|
|
5
|
+
Classifier: Intended Audience :: Developers
|
|
6
|
+
Classifier: License :: OSI Approved :: Apache Software License
|
|
7
|
+
Classifier: Programming Language :: Rust
|
|
8
|
+
Classifier: Programming Language :: Python :: 3
|
|
9
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
10
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
11
|
+
Classifier: Programming Language :: Python :: 3.14
|
|
12
|
+
Classifier: Programming Language :: Python :: Free Threading :: 3 - Stable
|
|
13
|
+
Classifier: Topic :: Internet :: WWW/HTTP :: HTTP Servers
|
|
14
|
+
Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
|
|
15
|
+
Requires-Dist: pytest>=8 ; extra == 'dev'
|
|
16
|
+
Requires-Dist: httpx>=0.27 ; extra == 'dev'
|
|
17
|
+
Provides-Extra: dev
|
|
18
|
+
License-File: LICENSE
|
|
19
|
+
Summary: A Rust-cored Python web framework where every route is also an agent tool.
|
|
20
|
+
Keywords: web,framework,api,agent,mcp,rust,free-threaded
|
|
21
|
+
Home-Page: https://github.com/slimboi34/web_cortex_framework
|
|
22
|
+
License: Apache-2.0
|
|
23
|
+
Requires-Python: >=3.12
|
|
24
|
+
Description-Content-Type: text/markdown; charset=UTF-8; variant=GFM
|
|
25
|
+
Project-URL: Changelog, https://github.com/slimboi34/web_cortex_framework/blob/main/CHANGELOG.md
|
|
26
|
+
Project-URL: Homepage, https://github.com/slimboi34/web_cortex_framework
|
|
27
|
+
Project-URL: Repository, https://github.com/slimboi34/web_cortex_framework
|
|
28
|
+
Project-URL: Security, https://github.com/slimboi34/web_cortex_framework/blob/main/SECURITY.md
|
|
29
|
+
|
|
30
|
+
# WebCortex
|
|
31
|
+
|
|
32
|
+
> **Status: pre-release.** Not yet published; build from source. Once released it
|
|
33
|
+
> installs as **`web-cortex-framework`** and imports as **`webcortex`** โ the same
|
|
34
|
+
> split as `djangorestframework` โ `import rest_framework`.
|
|
35
|
+
|
|
36
|
+
**๐ [Documentation](https://slimboi34.github.io/web_cortex_framework/)** ยท
|
|
37
|
+
[Tutorial](https://slimboi34.github.io/web_cortex_framework/tutorial/) ยท
|
|
38
|
+
[Use cases](https://slimboi34.github.io/web_cortex_framework/use-cases/) ยท
|
|
39
|
+
[Security](https://slimboi34.github.io/web_cortex_framework/security/)
|
|
40
|
+
|
|
41
|
+
A Python web framework with a Rust core, built on one idea:
|
|
42
|
+
|
|
43
|
+
> **If you declared it, Rust can run it โ and an agent can call it.**
|
|
44
|
+
|
|
45
|
+
Django and Rails were designed when the only client was a browser. Today the
|
|
46
|
+
client is just as likely to be a model. WebCortex treats that as the primary case
|
|
47
|
+
rather than something you bolt on with a second, hand-maintained tool server.
|
|
48
|
+
|
|
49
|
+
```python
|
|
50
|
+
# api.py
|
|
51
|
+
from webcortex import WebCortex
|
|
52
|
+
|
|
53
|
+
app = WebCortex("bookstore", database="sqlite://./app.db")
|
|
54
|
+
|
|
55
|
+
app.api_key("WEBCORTEX_API_KEY", id="service", scopes=["read", "write"])
|
|
56
|
+
app.rate_limit(per_second=50)
|
|
57
|
+
app.anonymous_scopes("read")
|
|
58
|
+
|
|
59
|
+
app.resource(
|
|
60
|
+
"books",
|
|
61
|
+
fields={"id": int, "title": str, "author": str, "year": int},
|
|
62
|
+
tools=True,
|
|
63
|
+
read_scopes=["read"],
|
|
64
|
+
write_scopes=["write"],
|
|
65
|
+
)
|
|
66
|
+
|
|
67
|
+
@app.get("/books/{id}/blurb", tool=True, scopes=["read"])
|
|
68
|
+
def blurb(id: int) -> str:
|
|
69
|
+
"""One-line pitch for a book."""
|
|
70
|
+
return f"Book {id} โ highly recommended."
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
```
|
|
74
|
+
$ webcortex dev
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
You now have a REST API, an OpenAPI 3.1 document, **a live MCP server exposing
|
|
78
|
+
all six endpoints as tools**, authentication, rate limiting, and security
|
|
79
|
+
headers. No second file, no schema written twice, no drift.
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
## Start here
|
|
84
|
+
|
|
85
|
+
```bash
|
|
86
|
+
# Not yet on PyPI โ see Status below. For now, build from source:
|
|
87
|
+
git clone https://github.com/slimboi34/web_cortex_framework && cd webcortex
|
|
88
|
+
uv venv --python 3.14 && uv pip install maturin && maturin develop --uv
|
|
89
|
+
|
|
90
|
+
webcortex new myapp # --template api | fullstack | agent | behaviour
|
|
91
|
+
cd myapp
|
|
92
|
+
export WEBCORTEX_API_KEY=$(webcortex keygen)
|
|
93
|
+
webcortex dev
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
## Why a Rust core, specifically
|
|
97
|
+
|
|
98
|
+
Most Rust-accelerated Python servers put Rust at the socket and call Python for
|
|
99
|
+
every request. You get faster parsing; your handler is still interpreted.
|
|
100
|
+
|
|
101
|
+
WebCortex puts the boundary somewhere more useful. **Python is a declaration
|
|
102
|
+
language that compiles to a plan the Rust runtime executes.** A route whose work
|
|
103
|
+
is expressible as data โ a query, a proxy, a rendered page, a static file, an
|
|
104
|
+
agent invocation โ runs entirely in Rust and *never enters the interpreter at
|
|
105
|
+
request time*. In practice that is most of a CRUD API.
|
|
106
|
+
|
|
107
|
+
```
|
|
108
|
+
$ webcortex check
|
|
109
|
+
12 routes, 9 served without touching Python
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
When a route genuinely needs Python, it crosses onto a pool of free-threaded
|
|
113
|
+
interpreter workers (CPython 3.13+/3.14, GIL disabled), each running its own
|
|
114
|
+
event loop. Handlers run in real parallel โ **measured at 4.82ร vs 1.38ร under
|
|
115
|
+
the GIL** ([DESIGN.md](DESIGN.md) has the numbers and their caveats).
|
|
116
|
+
|
|
117
|
+
WebCortex runs correctly on a GIL build too, and tells you which mode it is in.
|
|
118
|
+
|
|
119
|
+
## Behaviours
|
|
120
|
+
|
|
121
|
+
A "skill" written as a prompt is a *suggestion*. The model reads it and may
|
|
122
|
+
ignore it, and "if X then Y" fails silently when it does.
|
|
123
|
+
|
|
124
|
+
A **Behaviour** inverts that. The control flow is real Python โ a `for` loop is
|
|
125
|
+
a loop, an `if` is a branch, and both execute whether or not a model would have
|
|
126
|
+
chosen to. Only the *leaves* are probabilistic:
|
|
127
|
+
|
|
128
|
+
```python
|
|
129
|
+
@app.behaviour("triage", tools=["list_tickets", "update_tickets"],
|
|
130
|
+
max_steps=100, token_budget=100_000)
|
|
131
|
+
def triage(ctx, input):
|
|
132
|
+
"""Classify every open ticket and escalate the urgent ones."""
|
|
133
|
+
tickets = ctx.call("list_tickets", limit=50)
|
|
134
|
+
escalated = []
|
|
135
|
+
|
|
136
|
+
for ticket in tickets: # a real loop
|
|
137
|
+
verdict = ctx.ask( # a model call
|
|
138
|
+
f"Grade this ticket:\n{ticket['body']}",
|
|
139
|
+
schema={
|
|
140
|
+
"type": "object",
|
|
141
|
+
"properties": {
|
|
142
|
+
"urgency": {"type": "integer"},
|
|
143
|
+
"category": {"enum": ["bug", "billing", "other"]},
|
|
144
|
+
},
|
|
145
|
+
"required": ["urgency", "category"],
|
|
146
|
+
},
|
|
147
|
+
)
|
|
148
|
+
if verdict["urgency"] >= input.get("threshold", 7): # a real branch
|
|
149
|
+
escalated.append(ticket["id"])
|
|
150
|
+
ctx.call("update_tickets", id=ticket["id"], body=ticket["body"],
|
|
151
|
+
urgency=verdict["urgency"],
|
|
152
|
+
state="escalated" if ticket["id"] in escalated else "triaged")
|
|
153
|
+
|
|
154
|
+
return {"escalated": escalated, "usage": ctx.usage}
|
|
155
|
+
```
|
|
156
|
+
|
|
157
|
+
You get a procedure with **deterministic structure and probabilistic steps**,
|
|
158
|
+
rather than a probabilistic procedure.
|
|
159
|
+
|
|
160
|
+
`ctx` is how a behaviour reaches the world:
|
|
161
|
+
|
|
162
|
+
| | |
|
|
163
|
+
|---|---|
|
|
164
|
+
| `ctx.call(tool, **kwargs)` | invoke one of the app's tools, in-process |
|
|
165
|
+
| `ctx.ask(prompt, schema=...)` | a model call; a schema **forces** the shape, so branches switch on real values |
|
|
166
|
+
| `ctx.log(msg)` / `ctx.halt(reason)` | narrate or stop deliberately |
|
|
167
|
+
| `ctx.usage` / `ctx.trace` | budget consumed and every leaf executed, readable mid-run |
|
|
168
|
+
| `ctx.user` / `ctx.tools` | the delegated principal and what it may call |
|
|
169
|
+
|
|
170
|
+
**A behaviour is a tool.** It registers as a route, so it is automatically an
|
|
171
|
+
MCP tool, an OpenAPI operation, and something an agent โ or another behaviour โ
|
|
172
|
+
can call. Composition is just a tool call, so budgets and scopes still apply.
|
|
173
|
+
|
|
174
|
+
**The runtime enforces the limits, not your diligence:**
|
|
175
|
+
|
|
176
|
+
- `max_steps` caps total leaf operations. A loop that would run 100 times with
|
|
177
|
+
`max_steps=3` stops at 3 and returns `{"halted": true, "reason": ...}`.
|
|
178
|
+
- `token_budget` caps spend.
|
|
179
|
+
- A behaviour cannot call a tool it did not declare.
|
|
180
|
+
- An approval-gated tool cannot be laundered through a behaviour โ the gate
|
|
181
|
+
halts the run, exactly as it halts an agent.
|
|
182
|
+
- Scopes are delegated by intersection, never unioned.
|
|
183
|
+
|
|
184
|
+
```bash
|
|
185
|
+
webcortex new myapp --template behaviour
|
|
186
|
+
```
|
|
187
|
+
|
|
188
|
+
## The seven kinds of route
|
|
189
|
+
|
|
190
|
+
| Kind | Declared with | Runs in |
|
|
191
|
+
|---|---|---|
|
|
192
|
+
| Static | `app.static(...)` | Rust |
|
|
193
|
+
| Query | `app.query(...)`, `app.resource(...)` | Rust |
|
|
194
|
+
| Page | `app.page(...)` | Rust (minijinja) |
|
|
195
|
+
| Files | `app.static_files(...)` | Rust |
|
|
196
|
+
| Proxy | `app.proxy(...)` | Rust |
|
|
197
|
+
| Agent | `app.agent(..., expose_at=...)` | Rust |
|
|
198
|
+
| Behaviour | `@app.behaviour(...)` | Python worker pool |
|
|
199
|
+
| Python | `@app.get(...)` | Python worker pool |
|
|
200
|
+
|
|
201
|
+
## Every route is a tool
|
|
202
|
+
|
|
203
|
+
Mark a route `tool=True` and it appears in MCP `tools/list`, with an input
|
|
204
|
+
schema derived from the handler's own type hints. Agents declared in the same
|
|
205
|
+
app call those tools **in-process** โ a function call through the same
|
|
206
|
+
dispatcher the HTTP server uses, not a loopback request.
|
|
207
|
+
|
|
208
|
+
```python
|
|
209
|
+
app.agent(
|
|
210
|
+
"librarian",
|
|
211
|
+
model="claude-opus-5",
|
|
212
|
+
tools=["list_books", "get_books"],
|
|
213
|
+
scopes=["read"], # what a run may do
|
|
214
|
+
expose_scopes=["read"], # who may start one
|
|
215
|
+
max_steps=8,
|
|
216
|
+
token_budget=50_000,
|
|
217
|
+
expose_at="/ask",
|
|
218
|
+
)
|
|
219
|
+
```
|
|
220
|
+
|
|
221
|
+
A typo in `tools` fails at boot with a "did you mean" suggestion.
|
|
222
|
+
|
|
223
|
+
## What makes agents safe to deploy
|
|
224
|
+
|
|
225
|
+
These are enforced by the runtime, not by your diligence:
|
|
226
|
+
|
|
227
|
+
**Delegated authority.** An agent run executes as
|
|
228
|
+
`caller.delegate_to_agent(...)`, whose scopes are *intersected* with the
|
|
229
|
+
caller's โ never unioned. An anonymous caller cannot launch a privileged agent.
|
|
230
|
+
This is the confused-deputy defence, and it is a property of the type, not a
|
|
231
|
+
convention.
|
|
232
|
+
|
|
233
|
+
**Human approval gates.** Mark a route `approval="required"` and an agent asking
|
|
234
|
+
for it does not get it โ the run suspends and records an approval request. The
|
|
235
|
+
gate also applies to direct MCP calls, so it cannot be stepped around.
|
|
236
|
+
|
|
237
|
+
```python
|
|
238
|
+
@app.delete("/books/all", tool=True, scopes=["write"], approval="required")
|
|
239
|
+
def clear_catalogue(confirm: bool = False) -> dict: ...
|
|
240
|
+
```
|
|
241
|
+
|
|
242
|
+
**Runtime-enforced budgets.** `max_steps` and `token_budget` are checked before
|
|
243
|
+
each provider call. A looping model costs a bounded amount.
|
|
244
|
+
|
|
245
|
+
**Scope-filtered tool lists.** `tools/list` shows only what *that caller* can
|
|
246
|
+
invoke. A reader sees three tools where an admin sees six.
|
|
247
|
+
|
|
248
|
+
**A full audit trail**, including refused calls, at `GET /_webcortex/audit`.
|
|
249
|
+
|
|
250
|
+
## Security defaults
|
|
251
|
+
|
|
252
|
+
Deny-by-default throughout; relaxing something costs a line, tightening it costs
|
|
253
|
+
nothing. API keys are referenced by environment variable, hashed with SHA-256,
|
|
254
|
+
and compared in constant time. JWT (HS/RS) with mandatory expiry validation.
|
|
255
|
+
Per-principal token-bucket rate limiting. Security headers on every response.
|
|
256
|
+
CORS that refuses `*` with credentials *at boot*. Path traversal, symlink
|
|
257
|
+
escapes, and dotfiles refused by the static server.
|
|
258
|
+
|
|
259
|
+
`webcortex security` prints exactly what is reachable without a credential:
|
|
260
|
+
|
|
261
|
+
```
|
|
262
|
+
$ webcortex security
|
|
263
|
+
{"auth_configured": true, "public_routes": ["GET /"], "gated_tools": ["DELETE /books/all"]}
|
|
264
|
+
```
|
|
265
|
+
|
|
266
|
+
## The frontend, without the mess
|
|
267
|
+
|
|
268
|
+
Two clean paths sharing one data layer, chosen per route:
|
|
269
|
+
|
|
270
|
+
**Server-rendered pages**, executed in Rust:
|
|
271
|
+
|
|
272
|
+
```python
|
|
273
|
+
app.page("/", "index.html", sql="SELECT * FROM books LIMIT 20", bind="books")
|
|
274
|
+
app.static_files("/assets", "static")
|
|
275
|
+
```
|
|
276
|
+
|
|
277
|
+
The rule that keeps this clean: **a template receives a data object and nothing
|
|
278
|
+
else.** It has no database handle and cannot call Python, so it cannot grow
|
|
279
|
+
logic. Data is resolved *before* rendering, from a constant, a query, or a
|
|
280
|
+
Python handler. Autoescaping is on and derived from the file extension.
|
|
281
|
+
|
|
282
|
+
**A typed TypeScript client** for SPA frontends, from the same route table:
|
|
283
|
+
|
|
284
|
+
```bash
|
|
285
|
+
$ webcortex typegen # writes client/api.ts
|
|
286
|
+
```
|
|
287
|
+
|
|
288
|
+
Zero dependencies, `fetch`-based, with auth built in. Pages and static mounts
|
|
289
|
+
are excluded โ they are not part of the JSON API surface.
|
|
290
|
+
|
|
291
|
+
## Commands
|
|
292
|
+
|
|
293
|
+
```
|
|
294
|
+
webcortex new <name> scaffold a project (api | fullstack | agent | behaviour)
|
|
295
|
+
webcortex dev run with a startup report
|
|
296
|
+
webcortex check routes, tools, and the public attack surface
|
|
297
|
+
webcortex security what is reachable without a credential
|
|
298
|
+
webcortex tools the agent tool manifest
|
|
299
|
+
webcortex typegen generate a typed TypeScript client
|
|
300
|
+
webcortex openapi the OpenAPI 3.1 document
|
|
301
|
+
webcortex sql DDL for declared resources
|
|
302
|
+
webcortex keygen mint an API key
|
|
303
|
+
```
|
|
304
|
+
|
|
305
|
+
## Security
|
|
306
|
+
|
|
307
|
+
WebCortex has been through an adversarial review of its own controls โ auth,
|
|
308
|
+
authorization, injection, traversal, SSRF, exhaustion, disclosure โ plus stress
|
|
309
|
+
and soak testing. **Six issues were found and fixed**, each with a regression
|
|
310
|
+
test in `tests/test_pentest.py`:
|
|
311
|
+
|
|
312
|
+
| | Severity |
|
|
313
|
+
|---|---|
|
|
314
|
+
| Remote DoS + total auth failure via a JWT library panic | Critical |
|
|
315
|
+
| No panic boundary on the request path | High |
|
|
316
|
+
| Proxy path traversal usable as an SSRF primitive | High |
|
|
317
|
+
| Unbounded behaviour recursion exhausting the worker pool | High |
|
|
318
|
+
| Python tracebacks returned to clients | Medium |
|
|
319
|
+
| Client input faults reported as 500s | Low |
|
|
320
|
+
|
|
321
|
+
Soak: **1,786,805 requests, 0 errors, 0 panics**, memory at steady state.
|
|
322
|
+
|
|
323
|
+
[`SECURITY.md`](SECURITY.md) has the full report โ including what was *not*
|
|
324
|
+
tested and the known limits.
|
|
325
|
+
|
|
326
|
+
## Status
|
|
327
|
+
|
|
328
|
+
v0.3. Working and tested: the manifest IR, router, native ops (static / query /
|
|
329
|
+
proxy / page / files), the free-threaded Python bridge, authentication and
|
|
330
|
+
scopes, rate limiting, CORS, security headers, graceful shutdown, Behaviours,
|
|
331
|
+
the agent runtime with approval gates and budgets, the audit trail, OpenAPI, the
|
|
332
|
+
MCP server, and TypeScript generation. **251 tests** (66 Rust, 185 Python,
|
|
333
|
+
including a 54-test adversarial suite), clippy clean.
|
|
334
|
+
|
|
335
|
+
Not yet: Postgres, SSE streaming, durable agent runs, local model supervision.
|
|
336
|
+
See [DESIGN.md](DESIGN.md) for the roadmap, honest risk grading, and โ just as
|
|
337
|
+
importantly โ what is deliberately **not** being built.
|
|
338
|
+
|
|
339
|
+
## Known issue: CPython 3.14.7 with the GIL enabled
|
|
340
|
+
|
|
341
|
+
On CPython **3.14.7 specifically, with the GIL enabled**, the compiled extension
|
|
342
|
+
fails to import:
|
|
343
|
+
|
|
344
|
+
```
|
|
345
|
+
ValueError: module functions cannot set METH_CLASS or METH_STATIC
|
|
346
|
+
```
|
|
347
|
+
|
|
348
|
+
3.12, 3.13, 3.14.6 and the **free-threaded** 3.14.7 build (`3.14t`) are all
|
|
349
|
+
unaffected. 3.14.7 was released on 5 August 2026; the failure began the same day.
|
|
350
|
+
|
|
351
|
+
This is not a version-resolution accident on your machine โ `uv` resolves `3.14`
|
|
352
|
+
to the newest patch build available when it runs, so an environment that worked
|
|
353
|
+
yesterday can stop working today without anything in your project changing. Pin
|
|
354
|
+
to 3.13, or use the free-threaded 3.14 build, until this is resolved.
|
|
355
|
+
|
|
356
|
+
The investigation so far, including what has been ruled out, is in
|
|
357
|
+
[AGENTS.md ยง11](AGENTS.md#11-known-issue-cpython-3147-with-the-gil-enabled).
|
|
358
|
+
|
|
359
|
+
## For AI coding tools
|
|
360
|
+
|
|
361
|
+
[**AGENTS.md**](AGENTS.md) is the machine-facing reference: the complete API
|
|
362
|
+
surface with exact signatures and defaults, the binding and scope rules, the
|
|
363
|
+
constraints the runtime enforces, and the specific mistakes that are cheap to
|
|
364
|
+
make and expensive to debug. Claude Code, Cursor, Codex, Aider and Copilot
|
|
365
|
+
Workspace all read it by convention.
|
|
366
|
+
|
|
367
|
+
It is written to be correct rather than welcoming. Humans should start with the
|
|
368
|
+
[docs site](https://slimboi34.github.io/web_cortex_framework/) instead.
|
|
369
|
+
|
|
370
|
+
## Building from source
|
|
371
|
+
|
|
372
|
+
```bash
|
|
373
|
+
# 3.13 is the recommended toolchain today โ see "Known issue" above.
|
|
374
|
+
uv venv --python 3.13
|
|
375
|
+
uv pip install maturin pytest
|
|
376
|
+
.venv/bin/maturin develop --uv
|
|
377
|
+
.venv/bin/python -m pytest tests/
|
|
378
|
+
```
|
|
379
|
+
|
|
380
|
+
The free-threaded build is also supported and is the configuration the bridge was
|
|
381
|
+
designed around:
|
|
382
|
+
|
|
383
|
+
```bash
|
|
384
|
+
uv venv --python 3.14t
|
|
385
|
+
```
|
|
386
|
+
|
|
387
|
+
## License
|
|
388
|
+
|
|
389
|
+
Apache-2.0
|
|
390
|
+
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
web_cortex_framework-0.3.0.dist-info/METADATA,sha256=lAR2x6paiejmJE2GrLoDJn9r8cY_MagpCag1_dhRp5M,15456
|
|
2
|
+
web_cortex_framework-0.3.0.dist-info/WHEEL,sha256=z3sDn4xNPtieBDo9mUKkT1e80gbhCuRsQQi1_g6mdQM,97
|
|
3
|
+
web_cortex_framework-0.3.0.dist-info/entry_points.txt,sha256=93iJfcs9sw0ARrzvZ_88QBaO51j0nMcEABoEFJYzWuk,47
|
|
4
|
+
web_cortex_framework-0.3.0.dist-info/licenses/LICENSE,sha256=G2ZDBHXGF64oHA55EuVICzSok7So1NPaPQqL2HdpwQk,11545
|
|
5
|
+
web_cortex_framework-0.3.0.dist-info/sboms/webcortex-py.cyclonedx.json,sha256=CJ_mYPFwXSU1XQoynEozc85qoVBy7iqyuVR3J2YomD0,330569
|
|
6
|
+
webcortex/__init__.py,sha256=0UQ0c7U_nLmUGjVIUC-Z8hUJLX4_flf_L32twdiJNvA,817
|
|
7
|
+
webcortex/_bridge.py,sha256=GIJhMtwTnj1K4GjDq5fABdka-JPdIKO_YQtQcKIImCo,12738
|
|
8
|
+
webcortex/_core.cp313-win_amd64.pyd,sha256=V9w3BLUDRV6jo9-f61BUF9N-pYvs-nB-ubilYZAazoQ,12303360
|
|
9
|
+
webcortex/app.py,sha256=a2bF5w6Z8JDoVT_FArZfGEtqeN3nrIDg9_PKP58YFko,42138
|
|
10
|
+
webcortex/cli.py,sha256=TMPPGH1lAPBG1vQIL9OAGS9cm31wGSxWH3OtUjCkzFg,9354
|
|
11
|
+
webcortex/schema.py,sha256=HsQV65m4HgJGnKXn7O1gtytDEePhV8ZKtaMKZ4GExy0,7101
|
|
12
|
+
webcortex/starters.py,sha256=7rbjTLbiThNHR4etNO9SS12Kkj2AT3cmT5V3DiMvVcs,14899
|
|
13
|
+
web_cortex_framework-0.3.0.dist-info/RECORD,,
|
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this 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 Joshua Harty
|
|
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.
|