From 47b9bc9039b34ace7c66fcfefb89734fae8d1700 Mon Sep 17 00:00:00 2001 From: poli0981 <127664709+poli0981@users.noreply.github.com> Date: Tue, 18 Aug 2026 10:32:28 +0700 Subject: [PATCH] docs: the Security tab's spec and legal debt, including two claims that were false MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit SECURITY §6 has said since it was written that pip-audit "runs **from the tools venv**". The code has refused that since P2, with three tests enforcing the refusal, because `pip-audit`'s closure contains `msgpack` — no universal wheel, so a new CPython would hard-fail the whole sync under `--only-binary=:all:` and take Code Health down with a feature it does not use. §6 now describes the venv that exists. **And neither §6 nor PRD P1-1 could have been implemented as written.** Both promised a severity — §6 as "(CVE/GHSA id, severity, fixed-in)", the PRD as "severity-sorted" — against a field pip-audit has never had under either vulnerability service. Running the pinned 2.10.1 is what settled it: a finding carries `id`, `fix_versions`, `aliases` and `description`, full stop. Both are corrected to the order that ships, which is package → fixable → id, and both now say why a derived severity would be worse than none. `osv.dev` joins the opener allowlist, which ROADMAP has flagged as owed since 1.1.0 — without it every advisory link rejects and nothing opens, which is the silence SECURITY §4 exists to name. The description records what makes this entry different from `docs.astral.sh`: `PdHealthReport` hands over ruff's own `finding.url` verbatim, while `audit::advisory_url` **builds** the URL from an id checked against a whitelist that cannot contain a slash, colon, question mark, hash or percent. The tool chooses the id, never the destination. The three legal documents that said pip-audit is "not invoked in version 1.0" now say what it does, and DISCLAIMER §4's forward-looking sentence is replaced by one about a feature that exists: findings come from **PyPI's** advisory data, an advisory database is a record of what has been reported rather than a guarantee, and PipDock assigns no severity because pip-audit publishes none. **This re-shows the consent gate once** for every existing user — the mechanism working, not a regression. Also: UI-SPEC §4 gains the screen it has assumed since §3's diagram, §5 its click budget counted in the running app, and §6's off-list inventory said *four* while naming five — now six, plus the three from 1.1.0 it never named at all. CLI-SPEC §3 documents `pipdock audit` and drops `doctor`'s promise of an audit summary it has never printed. Co-Authored-By: Claude Opus 5 --- docs/CLI-SPEC.md | 3 ++- docs/CODE-HEALTH-SPEC.md | 2 +- docs/PRD.md | 2 +- docs/SECURITY.md | 10 +++++++-- docs/UI-SPEC.md | 25 ++++++++++++++++------ legal/DISCLAIMER.md | 2 +- legal/EULA.md | 2 +- legal/THIRD-PARTY-NOTICES.md | 2 +- src-tauri/capabilities/external-links.json | 5 +++-- 9 files changed, 37 insertions(+), 16 deletions(-) diff --git a/docs/CLI-SPEC.md b/docs/CLI-SPEC.md index 4acc29c..41e6d92 100644 --- a/docs/CLI-SPEC.md +++ b/docs/CLI-SPEC.md @@ -36,7 +36,8 @@ pipdock update [--all | ] pipdock uninstall [--force] # guard names each dependent and its constraint; --force overrides pipdock pin add|remove [--reason "…"] | pin list pipdock snapshot list | create | diff | rollback -pipdock doctor # engine check + env sanity + (P1) audit summary +pipdock doctor # engine check + env sanity +pipdock audit # known advisories in the selected environment; exit 1 on findings pipdock health [--path ] [--tool deptry|vulture|ruff] [--fix] # --fix = ruff only, prompts # --yes: proceeds on a clean tree, # REFUSES on a dirty one (exit 2) diff --git a/docs/CODE-HEALTH-SPEC.md b/docs/CODE-HEALTH-SPEC.md index afa9ef7..84cd330 100644 --- a/docs/CODE-HEALTH-SPEC.md +++ b/docs/CODE-HEALTH-SPEC.md @@ -31,7 +31,7 @@ Bootstrap: on first Health run (or pin-set change), create/sync the venv from `t - **pip unconditionally, not "the configured engine".** The venv is created with `python -m venv` and populated with pip whatever the user selected. uv is a preference about the *user's* environments; Health going dark with `PD-ENG-001` because uv is not on PATH would be a failure with no relation to what was asked for, and pip is present wherever Python is. - **No upper Python bound, and no `TOOLS_PYTHON_MAX`.** ROADMAP assumed "deptry ships compiled wheels; no cp314 wheel means an sdist build". deptry does ship a Rust extension but builds it against CPython's **stable ABI** (`deptry-0.25.1-cp310-abi3-win_amd64.whl`), verified installing on 3.12.10 and 3.14.6 from the same file; vulture and ruff are `py3-none-*`. The one version-tagged member of the closure, `tomli`, also publishes a `py3-none-any` fallback. The install passes `--only-binary=:all:`, so a future gap is a clean `PD-NET-011` rather than an sdist build ending at `PD-BLD-001` — which would tell someone who clicked *Health* to install Visual Studio Build Tools. -- **The repo's `tools/tools-requirements.txt` is the release-time ledger; the file written into `%LOCALAPPDATA%` is a rendering of it.** The ledger carries a fourth pin, `pip-audit`, for the post-1.0 Security tab (PRD P1-1). Health installs three. Rendering rather than copying is also what keeps the build machine's line endings out of the pin hash, which is taken over the *parsed* pin set for that reason. +- **The repo's `tools/tools-requirements.txt` is the release-time ledger; the file written into `%LOCALAPPDATA%` is a rendering of it.** The ledger carries a fourth pin, `pip-audit`, for the Security tab (PRD P1-1). Health installs three, and P1-1 did **not** change that: pip-audit ships in a venv of its own (`health::AUDIT_TOOLS`, `health::audit_dir`) so that its `msgpack` dependency — which publishes no universal wheel — can fail on a new CPython without taking Code Health down with it. `pins_for` renders each set separately, which is what keeps the two pin hashes independent: bumping one tool never re-syncs the other's venv. Rendering rather than copying is also what keeps the build machine's line endings out of the pin hash, which is taken over the *parsed* pin set for that reason. - **A sync rebuilds the venv rather than repairing it, and deletes `manifest.json` first.** `pip install -r` over satisfied pins is a no-op, so repairing a deleted `ruff.exe` installed nothing and then failed verification with `PD-HLT-001` — the state the code tells the user to re-sync out of. Deleting the manifest first means a torn sync reads as "never synced" rather than as a manifest claiming tools that are half-replaced. `python -m venv` exiting non-zero is **`PD-HLT-004`**, added in the same slice: `PD-NET-011` is `Area::Net` and would exit 6, so a script retrying on network failure would loop forever against a broken interpreter. diff --git a/docs/PRD.md b/docs/PRD.md index 17b23fb..a87a004 100644 --- a/docs/PRD.md +++ b/docs/PRD.md @@ -60,7 +60,7 @@ PipDock's thesis: **don't reimplement the resolver — explain it.** Wrap pip/uv | # | Feature | Notes | |---|---|---| -| P1-1 | Security tab | pip-audit (freeze-file mode) listing known CVEs per installed package, severity-sorted. | +| P1-1 | **Shipped 1.2.0.** Security tab | pip-audit (freeze-file mode) listing known advisories per installed package. **Not severity-sorted, because pip-audit has no severity field** — under either vulnerability service its findings carry only `id`, `fix_versions`, `aliases` and `description`, verified against the pinned 2.10.1. Ordered by package, then by whether anything *fixes* it, then by id: the one distinction that changes what the user can do. The CVE is an **alias**; the primary id is a `PYSEC-*`. | | P1-2 | Pin auto-suggest | **Shipped post-1.0 (P1-A).** Reverse-dependency count ≥ threshold (default 5, configurable in Settings; zero is off) ⇒ suggest pin with reason. Counts in-force edges only — extras and other-Python markers do not qualify a package. | | P1-3 | **Shipped 1.1.0.** Export / import | `requirements.txt` and `constraints.txt` export; import-as-queue. | | P1-4 | **Partly shipped, 1.1.0.** Cache manager | Shows and clears **PipDock's own** disk usage: snapshots and the Code Health tools venv. `index.db` is reported but not clearable — it holds settings, pins and the consent record in the same file, so "clear the cache" must never take them. **The engine caches (`pip cache`, `uv cache`) are not covered** and are a separate item: they belong to the engine, live outside `%LOCALAPPDATA%\PipDock\`, and purging them is a subprocess rather than a file delete. | diff --git a/docs/SECURITY.md b/docs/SECURITY.md index 2fde5e0..57d9f2f 100644 --- a/docs/SECURITY.md +++ b/docs/SECURITY.md @@ -30,7 +30,7 @@ Environments carrying an `EXTERNALLY-MANAGED` marker are **blocked by default** `pypi.org` is the **only** host PipDock itself connects to. It does not update itself (§5), so it has no reason to reach `github.com` — the legal gate and the bug-report deep link hand a URL to the user's browser rather than fetching anything. The webview cannot reach either: `connect-src` in `tauri.conf.json` allows only `'self'` and the IPC origin, so all network access goes through Rust. -**Three hosts may be handed to the browser, and the allowlist is the record of why.** `capabilities/external-links.json` scopes `opener:allow-open-url` to `https://github.com/*`; to `https://docs.astral.sh/*` since Phase 3 · P4 — every ruff finding carries its own rule page and CODE-HEALTH-SPEC §6 as amended requires using ruff's `url` rather than constructing one; and to `https://poli0981.dev/*` since Phase 4, for the one page the About tab links to that lists every other way to reach the author. None is a connection PipDock makes; all three are URLs it asks the OS to open. The widening is recorded here rather than only in `capabilities/` because an allowlist entry is a change to this document's subject matter, not a config detail — and because the failure mode of *not* widening it is silent: the promise rejects, nothing opens, and nothing anywhere says so. +**Three hosts may be handed to the browser, and the allowlist is the record of why.** `capabilities/external-links.json` scopes `opener:allow-open-url` to `https://github.com/*`; to `https://docs.astral.sh/*` since Phase 3 · P4 — every ruff finding carries its own rule page and CODE-HEALTH-SPEC §6 as amended requires using ruff's `url` rather than constructing one; and to `https://osv.dev/*` since P1-1, where every advisory links to its entry and the alternative was a promise that rejects in silence; and to `https://poli0981.dev/*` since Phase 4, for the one page the About tab links to that lists every other way to reach the author. None is a connection PipDock makes; all three are URLs it asks the OS to open. The widening is recorded here rather than only in `capabilities/` because an allowlist entry is a change to this document's subject matter, not a config detail — and because the failure mode of *not* widening it is silent: the promise rejects, nothing opens, and nothing anywhere says so. **What the scope actually defends is narrower than it looks.** Most call sites pass module constants no injected string can reach. Two pass data: `PdErrorRow` hands over a URL built in Rust, and `PdHealthReport` hands over `finding.url` — which comes out of **ruff's own JSON** over the user's source tree, and is the only URL in the application derived from a third-party tool's output. `https://docs.astral.sh/*` is precisely what stops that being anything else. That is also why the contact addresses in About are copied to the clipboard rather than opened: a `mailto:` entry would widen the allowlist by a whole URL *scheme*, and re-open a target class for that one call site, to save a paste. @@ -48,7 +48,13 @@ Consequences worth knowing: there is no signing keypair to generate or rotate, n ## 6. Auditing user environments (P1 Security tab) -pip-audit runs **from the tools venv** in freeze-file mode: snapshot-freeze the target env → `pip-audit -r --no-deps --format json` → findings joined to installed rows (CVE/GHSA id, severity, fixed-in). Exact flags validated in spike SP-4 (pip-audit's foreign-env options evolve). Findings link to the OSV entry; "update to fixed version" hands off to the normal Update flow — audit never auto-applies anything. +pip-audit runs **from a venv of its own** in freeze-file mode: `Engine::freeze` the target env → `pip-audit -r --no-deps -f json` → findings joined to installed rows. Flags validated in SP-4 and pinned by a committed capture (`tests/fixtures/audit/`). + +**Its own venv, not Code Health's**, and that is a correction rather than a detail. This section said "the tools venv" from the day it was written; the code has refused that since P2, because `pip-audit`'s closure contains `msgpack`, which publishes no universal wheel and would hard-fail the whole sync under `--only-binary=:all:` on a new CPython — taking Code Health down with a feature it does not use. `health::AUDIT_TOOLS` and `health::audit_dir` keep the blast radius inside the Security tab. + +**No severity, because pip-audit has none.** This section promised "(CVE/GHSA id, severity, fixed-in)" against a field that does not exist under either vulnerability service; a finding carries `id`, `fix_versions`, `aliases` and `description` and nothing else. Findings are ordered by package, then by whether anything fixes them, then by id. A severity derived from the id's year or the prose would be a number PipDock invented, shown beside real ones. + +**The network surface does not change.** pip-audit's *default* service is PyPI, and it is left there deliberately: §4's table still has one row. Findings **link** to the OSV entry, which is a visit the user's browser makes after a click, and the URL is **built from a validated id** rather than taken from the tool's output. "Update to fixed version" hands off to the normal Update flow — audit never auto-applies anything. ## 7. Supply chain of PipDock itself diff --git a/docs/UI-SPEC.md b/docs/UI-SPEC.md index ce6c453..cc7bbba 100644 --- a/docs/UI-SPEC.md +++ b/docs/UI-SPEC.md @@ -139,6 +139,16 @@ the snapshot's side. **Health.** Project-folder picker (persisted per env) → run panel with three result tabs (deptry / vulture / ruff) per CODE-HEALTH-SPEC; `Fix with ruff` gated behind explicit confirm listing file count. +**Security.** *Run audit* → advisories grouped by package, each with its id, the versions that fix +it (or **no fix**, stated rather than left blank), its aliases — which is where the CVE lives, since +pip-audit's primary id is a `PYSEC-*` — the advisory prose verbatim, and a link to its OSV entry. +**No severity column**: pip-audit publishes none under either vulnerability service, so the order is +package → fixable → id, and inventing a severity would put a number PipDock made up beside real +ones (PRD P1-1 is amended to say so). A *Cancel* appears while a run is going, which Code Health has +no equivalent of: an audit is 18-68 s against Health's 1.3 s. **The body says nothing while a run is +in flight** — not "no audit has run", which is what it said until someone clicked Run against a slow +bridge and read it. + **Settings.** Engine (pip/uv radio + detected versions), locale (EN/VI), **pin auto-suggest count** (P1-A; zero turns suggestions off), snapshot retention, index refresh, PEP 668 override (off by default, scary copy), *Open logs folder*. **Disk usage** (P1-C) shows what PipDock has written — snapshots and the Code Health tools venv, each with a *Clear*, and `index.db` reported without one because it holds settings, pins and the consent record in the same file. Three artefacts, not four: there are no log files, `LOG_RETENTION_DAYS` has never had a reader, and a "logs — 0 B" row would invent one. @@ -168,6 +178,7 @@ app lands. Counted by hand in the running app, never inferred from the markup. | Switch engine | **3** | Settings → engine radio → (auto-saved) back | | Run Code Health | **3** | Health → Run (folder persisted) → view (**4** the first time in a project: Health → *Choose folder…* → the OS dialog, which is not PipDock's click → Run → view. The folder is remembered per environment from then on.) | | Fix ruff findings | **3** | ruff tab → *Fix N…* → *Fix* (from a report already on screen; **5** from the landing screen with a folder remembered, which is the owner's ceiling). Cancel holds default focus, so `Enter` without `Tab` cancels. | +| Run a security audit | **2** | Security → *Run audit*. Counted in the running app against a stubbed bridge. The first run also builds the audit environment, which is a wait rather than a click. | | Upgrade pip | **2** | *Upgrade pip* → *Upgrade* (Environments is the landing screen, so no tab click). The button appears only when pip is below the 22.2 planner floor — the case the ordinary Updates path cannot fix, because the planner it needs will not run. | ### Shell rules established by the first installed build (2026-08-13) @@ -201,12 +212,14 @@ a metre of empty surface. Still resizable, and `minWidth`/`minHeight` are unchan `PdEnvSwitcher` alone, which nothing needs while the header shows the selected interpreter and the Environments tab switches it. (ROADMAP and CLAUDE.md both claimed 16 of 16 after S4; the count had quietly folded in components that are not on -this list.) Four components not on this list have -turned out to be load-bearing and are listed here so the inventory stays honest: `PdErrorRow` -(ERROR-CATALOG §3's row, used by every error surface), `PdDialog` (the shared modal §7's destructive -confirms need), `PdUninstallDialog` (§5's three options), `PdPinChip` (the 🔒 chip, shared by the -table and the Pins screen) and `PdRollbackPreview` (DATA-FLOW §8's preview, including its -`PD-SNP-002` list). +this list.) **Six** components not on this list have +turned out to be load-bearing and are listed here so the inventory stays honest — the number said +*four* while naming five for two milestones, which is the counting trap this section exists to +avoid: `PdErrorRow` (ERROR-CATALOG §3's row, used by every error surface), `PdDialog` (the shared +modal §7's destructive confirms need), `PdUninstallDialog` (§5's three options), `PdPinChip` (the +🔒 chip, shared by the table and the Pins screen), `PdRollbackPreview` (DATA-FLOW §8's preview, +including its `PD-SNP-002` list) and `PdAuditReport` (P1-1's advisory list). Three more shipped in +1.1.0 and are named nowhere in this section: `PdCacheUsage`, `PdPalette` and `PdRequirements`. ## 7. States & feedback diff --git a/legal/DISCLAIMER.md b/legal/DISCLAIMER.md index fc9386d..c62a8b6 100644 --- a/legal/DISCLAIMER.md +++ b/legal/DISCLAIMER.md @@ -16,7 +16,7 @@ PipDock blocks modification of externally-managed (PEP 668) Python installations ## 4. Information accuracy -Package metadata, latest-version information and code-health reports are derived from third-party sources (PyPI, and deptry/vulture/ruff output) and from heuristics such as reverse-dependency analysis. They may be incomplete, outdated, or wrong — for example, dead-code detection produces false positives on dynamically referenced code, and deptry reports a module name rather than the distribution that provides it. **Review before acting**; PipDock's reports are assistance, not authority. Version 1.0 ships no vulnerability scanning; if a future release adds it, its findings come from the OSV database and this paragraph covers them too. +Package metadata, latest-version information and code-health reports are derived from third-party sources (PyPI, and deptry/vulture/ruff output) and from heuristics such as reverse-dependency analysis. They may be incomplete, outdated, or wrong — for example, dead-code detection produces false positives on dynamically referenced code, and deptry reports a module name rather than the distribution that provides it. **Review before acting**; PipDock's reports are assistance, not authority. The Security tab reports known advisories against your installed packages. Those come from **PyPI's advisory data**, by way of pip-audit, and are covered by this paragraph too: an advisory database is a record of what has been reported, not a guarantee that a package is safe or that an absence of findings means there is nothing to find. Each finding links to its entry on osv.dev so you can read the original. PipDock assigns no severity and no risk score, because pip-audit publishes none. ## 5. Not professional advice; no affiliation diff --git a/legal/EULA.md b/legal/EULA.md index 936900e..56ca86a 100644 --- a/legal/EULA.md +++ b/legal/EULA.md @@ -8,7 +8,7 @@ PipDock is free software, licensed under the **GNU General Public License, versi ## 2. What PipDock does (acknowledgment) -PipDock installs, upgrades, and removes packages in Python environments **at your direction**, by invoking third-party package managers (pip, uv) and analysis tools (deptry, vulture, ruff; pip-audit is planned and is not invoked in version 1.0). These operations modify software environments on your computer and can affect the behavior of your projects. You are responsible for reviewing each preview and confirmation the application presents before applying changes. +PipDock installs, upgrades, and removes packages in Python environments **at your direction**, by invoking third-party package managers (pip, uv) and analysis tools (deptry, vulture, ruff, and pip-audit for the Security tab). These operations modify software environments on your computer and can affect the behavior of your projects. You are responsible for reviewing each preview and confirmation the application presents before applying changes. ## 3. No warranty diff --git a/legal/THIRD-PARTY-NOTICES.md b/legal/THIRD-PARTY-NOTICES.md index b352a07..26a2813 100644 --- a/legal/THIRD-PARTY-NOTICES.md +++ b/legal/THIRD-PARTY-NOTICES.md @@ -45,7 +45,7 @@ These run as independent programs from your system or from PipDock's isolated to | deptry | MIT | Code Health — dependency issues | | vulture | MIT | Code Health — dead code | | ruff | MIT | Code Health — lint/format | -| pip-audit | Apache-2.0 | Security tab — **not invoked in 1.0**; listed because the tab is planned and this row is where it will belong | +| pip-audit | Apache-2.0 | Security tab — known advisories against installed packages. Installed into its own environment, separate from the three above | | CPython | PSF License | the environments themselves | ## C. Services diff --git a/src-tauri/capabilities/external-links.json b/src-tauri/capabilities/external-links.json index 926f7aa..8dd2edd 100644 --- a/src-tauri/capabilities/external-links.json +++ b/src-tauri/capabilities/external-links.json @@ -1,7 +1,7 @@ { "$schema": "../gen/schemas/desktop-schema.json", "identifier": "external-links", - "description": "Hand a GitHub, ruff-docs or poli0981.dev URL to the user's browser. GitHub: the legal gate links to the five documents (UI-SPEC §4), the summary sheet's Report-bug deep link opens a prefilled issue (ERROR-CATALOG §4), PD-SYS-001 links to the long-paths help, vulture's whitelist help lives there too, and About links to the repository. docs.astral.sh: every ruff finding carries its own rule page, which CODE-HEALTH-SPEC §6 as amended says is keyed by rule NAME and must be used rather than constructed. poli0981.dev: About's links page, the one page listing every other way to reach the author. The webview cannot do this itself: connect-src in tauri.conf.json allows only 'self' and the IPC origin. STILL SCOPED ON PURPOSE — an unscoped opener is a launch-anything primitive reachable from any injected string, which is the same reasoning SECURITY §2 applies to argv arrays. Three hosts is not the same as any host, and each was added because a feature failed silently without it, not to make room. WHAT THIS ACTUALLY DEFENDS is narrower than it looks: most call sites pass module constants no injected string can reach. Two pass data — PdErrorRow's Rust-built URL, and PdHealthReport's finding.url, which comes out of ruff's own JSON over the user's source tree and is the only URL in the application derived from a third-party tool's output. That is the one this list is really bounding, and the reason About copies its contact addresses to the clipboard instead of opening them: a mailto: entry would widen the list by a whole URL scheme and re-open a target class for that call site, to save a paste.", + "description": "Hand a GitHub, ruff-docs, poli0981.dev or OSV URL to the user's browser. GitHub: the legal gate links to the five documents (UI-SPEC §4), the summary sheet's Report-bug deep link opens a prefilled issue (ERROR-CATALOG §4), PD-SYS-001 links to the long-paths help, vulture's whitelist help lives there too, and About links to the repository. docs.astral.sh: every ruff finding carries its own rule page, which CODE-HEALTH-SPEC §6 as amended says is keyed by rule NAME and must be used rather than constructed. poli0981.dev: About's links page, the one page listing every other way to reach the author. The webview cannot do this itself: connect-src in tauri.conf.json allows only 'self' and the IPC origin. STILL SCOPED ON PURPOSE — an unscoped opener is a launch-anything primitive reachable from any injected string, which is the same reasoning SECURITY §2 applies to argv arrays. Four hosts is not the same as any host, and each was added because a feature failed silently without it, not to make room. WHAT THIS ACTUALLY DEFENDS is narrower than it looks: most call sites pass module constants no injected string can reach. Two pass data — PdErrorRow's Rust-built URL, and PdHealthReport's finding.url, which comes out of ruff's own JSON over the user's source tree and is the only URL in the application derived from a third-party tool's output. osv.dev: every Security-tab finding carries an advisory entry, which DISCLAIMER §4 and SECURITY §6 both promise a link to — without this the promise rejects and nothing opens, silently. That URL is the SECOND derived from a tool's output, and it is deliberately not the same kind: PdHealthReport hands over ruff's own `finding.url` verbatim, while `audit::advisory_url` BUILDS the URL from an id it has checked against a whitelist of ASCII alphanumerics and hyphen. Nothing that passes that check can contain a slash, colon, question mark, hash or percent, so the result cannot be anything but a path segment under one host — the tool chooses the id, never the destination. That is the one this list is really bounding, and the reason About copies its contact addresses to the clipboard instead of opening them: a mailto: entry would widen the list by a whole URL scheme and re-open a target class for that call site, to save a paste.", "windows": ["main"], "permissions": [ { @@ -9,7 +9,8 @@ "allow": [ { "url": "https://github.com/*" }, { "url": "https://docs.astral.sh/*" }, - { "url": "https://poli0981.dev/*" } + { "url": "https://poli0981.dev/*" }, + { "url": "https://osv.dev/*" } ] } ]