security-knowledge-os 0.1.0__tar.gz → 0.2.0__tar.gz

security_knowledge_os-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,41 @@
+name: CI
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      # TODO: pin these actions to a full commit SHA for supply-chain safety.
+      - uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+          fetch-depth: 0 # full history (the manifest-ancestor check needs it)
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Install (pinned)
+        run: pip install -e ".[api,llm,dev]" -c constraints.txt
+      # Mirrors the project's own gate (scripts/preflight.py runs `ruff check`,
+      # not `ruff format --check`), so CI enforces exactly what the repo commits
+      # to. (`ruff format --check` is not run repo-wide yet - a separate cleanup.)
+      - name: Ruff (lint)
+        run: ruff check .
+      - name: Mypy (strict)
+        run: mypy
+      # Two tests assert the tracked sbom.json matches the *exact* installed
+      # dependency closure of the maintainer's environment (e.g. build-time
+      # packages like trove-classifiers); they cannot pass in an arbitrary CI
+      # runner and are verified locally via scripts/preflight.py before a
+      # release. Everything else - including the manifest-ancestor check - runs.
+      - name: Tests
+        run: >
+          pytest -q
+          --deselect tests/unit/test_generate_sbom.py::test_no_unknown_licences_for_a_real_specific_osi_classifier
+          --deselect tests/unit/test_preflight_manifest.py::test_real_tracked_sbom_matches_the_current_environment

security_knowledge_os-0.2.0/.github/workflows/publish.yml

@@ -0,0 +1,52 @@
+name: Publish to PyPI
+
+# Publishes on a version tag (e.g. `v0.1.1`). Uses PyPI Trusted Publishing
+# (OIDC) - NO API token / secret is stored in the repo. One-time setup on
+# PyPI: project -> Publishing -> add a GitHub trusted publisher for
+# repo `kagioneko/security-knowledge-os`, workflow `publish.yml`,
+# environment `pypi`. Until that is configured the publish JOB simply FAILS
+# (it is not skipped) and nothing is uploaded - a failed release, never a
+# silent or partial one.
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      # TODO: pin these actions to a full commit SHA for supply-chain safety.
+      - uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Verify the tag matches the packaged version
+        run: |
+          pip install build
+          python -m build
+          tag="${GITHUB_REF_NAME#v}"
+          pkg=$(ls dist/*.whl | sed -E 's/.*-([0-9]+\.[0-9]+\.[0-9]+)-.*/\1/')
+          echo "tag=$tag packaged=$pkg"
+          test "$tag" = "$pkg"
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write # OIDC token for PyPI Trusted Publishing
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

{security_knowledge_os-0.1.0 → security_knowledge_os-0.2.0}/PKG-INFO

@@ -1,11 +1,12 @@
 Metadata-Version: 2.5
 Name: security-knowledge-os
-Version: 0.1.0
+Version: 0.2.0
 Summary: Deterministic security assessment engine + knowledge retrieval + optional LLM assistance
 License-Expression: Apache-2.0
 License-File: LICENSE
 License-File: NOTICE
 Requires-Python: >=3.12
+Requires-Dist: cryptography>=50.0
 Requires-Dist: pydantic>=2.6
 Requires-Dist: pyyaml>=6.0
 Provides-Extra: api
@@ -25,6 +26,15 @@ Description-Content-Type: text/markdown
 
 # Security Knowledge OS
 
+[![PyPI](https://img.shields.io/pypi/v/security-knowledge-os)](https://pypi.org/project/security-knowledge-os/)
+[![Python](https://img.shields.io/pypi/pyversions/security-knowledge-os)](https://pypi.org/project/security-knowledge-os/)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue)](LICENSE)
+
+```bash
+pip install security-knowledge-os
+skos assess your-agent.yaml   # deterministic, offline by default; bundled rules/knowledge
+```
+
 > **Language note / 言語について**: This repository (code, docs, commit history) is
 > **English-first by design** — it is written to be consumed by AI coding agents and
 > cites international standards (OWASP, MITRE ATLAS, NIST) directly. The section
@@ -138,7 +148,18 @@ treated as data, never as a control instruction. Details in
 | **M7 — Fixtures + Evaluation + starter KUs** | done | `knowledge/public/**` (14 KUs), `tests/fixtures/assessments/{safe,vulnerable,unknown}/`, `app/eval/metrics.py`, `scripts/evaluate.py`, JA retrieval (trigram) |
 | **M8 — Docs + hardening** | done | Security disclaimer (AC-15–18), KU `provenance` schema, `docs/{attribution,threat-model,architecture}.md`, `sbom.json`, `scripts/{secret_scan,generate_sbom,preflight}.py` |
 
-## Quickstart (M1)
+## Install
+
+Requires **Python 3.12+**. From PyPI (ships the default rules / knowledge /
+safe-test data, so `skos assess` works with no checkout):
+
+```bash
+pip install security-knowledge-os          # engine + CLI
+pip install "security-knowledge-os[api]"   # + the local FastAPI app
+skos assess your-agent.yaml                # your-agent.yaml is an input you write
+```
+
+## Quickstart (M1, from a source checkout)
 
 ```bash
 python3.12 -m venv .venv

{security_knowledge_os-0.1.0 → security_knowledge_os-0.2.0}/PUBLICATION_MANIFEST.md

@@ -1,16 +1,16 @@
-# Publication Manifest — Security Knowledge OS v0.1.0
+# Publication Manifest — Security Knowledge OS v0.2.0
 
 Snapshot of what the first public push contains. Generated for the pre-publication
 review; regenerate with `git ls-files` after any change.
 
-- Commit: `4c004ab` (packaging: bundle default data into the wheel + config fallback so pip install works standalone; allowlist guard rejects private/hidden/symlink incl. ancestor symlinks; sdist ships only tracked public files; cross-review PASS round 38, not yet pushed)
+- Commit: `316e8c6` (v0.2.0: Update Packs + `skos scan mcp`; PyPI 0.1.0 was `a7f463d`)
 - History: rewritten once on 2026-09-20, before first publication, to normalise author/committer identity to the
   GitHub no-reply address (one commit message also scrubbed of a local account name). Every commit's tree is
   identical before and after, so the reviewed content is the published content; commit hashes cited in the
   review records below are the **pre-rewrite** ones - see `docs/history-rewrite-map.md` for old -> new.
 - Licence: **Apache-2.0** (`LICENSE`, `NOTICE`, `pyproject.toml`)
-- Tracked files: **218**
-- Tests: **792** items (791 pass, 1 skip = JA-R02)
+- Tracked files: **242**
+- Tests: **943** items (942 pass, 1 skip = JA-R02)
 - `scripts/preflight.py`: **PASS** (now also verifies the documented
   quickstart `pip install -e` command installs every declared extra,
   pins `constraints.txt`, AND passes `--build-constraint constraints.txt`
@@ -19,7 +19,7 @@ review; regenerate with `git ls-files` after any change.
   environment, ignoring only its timestamp, without preflight itself
   rewriting that tracked file to check it, round 11 Codex#12)
 - Cross-AI review: Codex (code audit) + Antigravity (adversarial design
-  audit), **thirty-eight rounds** (through round-38), 2026-09-11 -- 2026-09-26. Rounds 1-2
+  audit), **thirty-nine rounds** (through round-39), 2026-09-11 -- 2026-09-26. Rounds 1-2
   (2026-09-11): CHANGES-REQUIRED both times, 19 then 13 findings, all
   fixed — see `REVIEW_CHECKLIST.md` sign-off tables. Rounds 3-6
   (2026-09-12): CHANGES-REQUIRED each time, independent findings each
@@ -774,6 +774,30 @@ review; regenerate with `git ls-files` after any change.
   pytest test run by the release gate) fixed in `4c004ab` (comment only). This is
   the packaging change's cross-review PASS for the PyPI release.
 
+  **Round 39** (2026-09-26, post-publication: reviewed the README PyPI
+  badges/install additions and the new test CI workflow before pushing them):
+  Codex **PASS-with-nits** - no secrets, no dangerous CI settings (contents:
+  read, no pull_request_target, no secret use on untrusted PRs). Nits applied:
+  `persist-credentials: false` on checkout (+ a SHA-pin TODO), and README notes
+  Python 3.12+ and that the assessed YAML is a user-provided input.
+
+  **v0.2.0 Update Packs review** (2026-09-28, scoped to the change set
+  `master..488e0f6`: `app/packs/`, `app/pack_cli.py`, `app/adapters/mcp_config.py`,
+  `app/reviewer/{vocabulary,extensions}.py`, `docs/pack-schema.md`, plus the
+  separate data-only pack source `skos-pack-mcp`). Codex, four rounds, each
+  CHANGES-REQUIRED and fully or partly fixed: round 1 (`c14bc7f`) 16 findings
+  (4 HIGH), round 2 (`30840b5`) 8 new (3 HIGH), round 3 (`6cb990e`) 4 new
+  (1 HIGH), round 4 (`771d870`) 2 new (MEDIUM F29, LOW F30) plus a residual HIGH
+  (F25: a lost `installed.json` made a weakening update look like a first
+  install). F25/F29/F30 fixed in `2e0e99c`; that commit reviewed by
+  Antigravity: **PASS-with-nits**, the one documentation nit fixed in
+  `488e0f6`. Accepted as known limitations (recorded, not fixed): F08
+  (`npm exec` trailing options / `npm_config_registry` still inherit a known
+  package profile in `skos scan mcp`), F26 (same-version replacement drops the
+  displaced copy before the registry commit), F28 (a credential reference or
+  empty value in a URL, or a flag with no value, is reported as a literal
+  secret - a false positive).
+
 ## Tracked files by area
 
 Per-area counts below were last verified at round 2 (commit `bcd9519`) and
@@ -783,20 +807,20 @@ check enforces (total tracked files, total tests) are kept current above.
 
 | area | files | notes |
 | --- | --- | --- |
-| `app/` | 59 (.py) | engine, models, policy, retrieval, reviewer, llm, storage, eval, cli, main |
-| `tests/` | 83 | 52 test modules + fixtures |
+| `app/` | 76 (.py) | engine, models, policy, retrieval, reviewer, llm, storage, eval, cli, main, packs (Update Pack manager), adapters (MCP config scan) |
+| `tests/` | 86 | 55 test modules + fixtures |
 | `knowledge/` | 24 | 14 public KUs + `private/` skeleton (README + 2 `.gitkeep`) + category `.gitkeep`s |
 | `rules/` | 13 | 7 rule YAMLs + category `.gitkeep`s |
 | `safe_tests/` | 4 | 4 vetted templates |
-| `scripts/` | 12 | validators, ingest/build_index, assess, evaluate, sbom, secret_scan, preflight, cross-review runner |
-| `docs/` | 9 | see below |
+| `scripts/` | 13 | validators, ingest/build_index, assess, evaluate, sbom, secret_scan, preflight, cross-review runner, issue_license |
+| `docs/` | 11 | see below |
 | `reviews/` | 2 | `.gitignore` + `README.md` only — cross-review output `.md`/`.log` files are gitignored, never tracked |
 | root | 11 | `README.md`, `LICENSE`, `NOTICE`, `pyproject.toml`, `.gitignore`, `.env.example`, `constraints.txt`, `sbom.json` |
 | review docs | 3 | `REVIEW_PACKAGE.md`, `REVIEW_CHECKLIST.md`, `PUBLICATION_MANIFEST.md` |
 
 Docs: `architecture`, `threat-model`, `safety-boundaries`, `knowledge-schema`,
 `rule-schema`, `safe-test-schema`, `knowledge-corpus`, `attribution`,
-`acceptance-criteria`.
+`acceptance-criteria`, `history-rewrite-map`, `pack-schema`.
 
 ## Explicitly excluded (in `.gitignore`)
 
@@ -868,7 +892,7 @@ Safe-test templates (4): `ST-IPI-001`, `ST-MEM-001`, `ST-TOOL-001`, `ST-CRED-001
 
 ## Dependencies (`sbom.json`)
 
-63 components — the project's actual dependency closure (Codex#9, round 7:
+66 components — the project's actual dependency closure (Codex#9, round 7:
 walked outward from every declared root rather than listing every
 installed distribution, which also included `pip` and unrelated
 environment packages; Codex#9, round 8: a package reachable only
@@ -880,7 +904,9 @@ one that is itself a *direct* pyproject.toml entry; Codex#6, round 14:
 requirement, round 9's own fix, had discarded which extras a PARENT
 requirement actually activated on its dependency, hiding this one).
 Core install =
-`pydantic` + `pyyaml`; the rest are `[api]`/`[llm]` extras or dev/test-only.
+`pydantic` + `pyyaml` + (v0.2.0, Update Pack signatures) `cryptography`
+(Apache-2.0 OR BSD-3-Clause) with its dependencies `cffi` (MIT-0) and
+`pycparser` (BSD-3-Clause); the rest are `[api]`/`[llm]` extras or dev/test-only.
 Zero `UNKNOWN` licences. Licences present: MIT, BSD (2/3-Clause), Apache-2.0,
 PSF-2.0 — permissive — plus **`pathspec` and `certifi`, both under MPL-2.0**
 (Codex finding #10, round 2, 2026-09-11, corrected round 3, 2026-09-12: an
@@ -897,7 +923,7 @@ which use Python's native `truststore` instead of `certifi`); `pathspec`
 is a transitive dependency of `mypy` (**not** `ruff`, which declares no
 dependencies of its own per installed-environment metadata) — both
 dev/test-only or extras, never imported by, bundled with, or distributed
-as part of `app/`'s core install. None of the 63 components conflict with
+as part of `app/`'s core install. None of the 66 components conflict with
 Apache-2.0 distribution of this project. Full list in `sbom.json`.
 
 ## §24 evaluation (internal fixtures — not real-world performance)

{security_knowledge_os-0.1.0 → security_knowledge_os-0.2.0}/README.md

@@ -1,5 +1,14 @@
 # Security Knowledge OS
 
+[![PyPI](https://img.shields.io/pypi/v/security-knowledge-os)](https://pypi.org/project/security-knowledge-os/)
+[![Python](https://img.shields.io/pypi/pyversions/security-knowledge-os)](https://pypi.org/project/security-knowledge-os/)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue)](LICENSE)
+
+```bash
+pip install security-knowledge-os
+skos assess your-agent.yaml   # deterministic, offline by default; bundled rules/knowledge
+```
+
 > **Language note / 言語について**: This repository (code, docs, commit history) is
 > **English-first by design** — it is written to be consumed by AI coding agents and
 > cites international standards (OWASP, MITRE ATLAS, NIST) directly. The section
@@ -113,7 +122,18 @@ treated as data, never as a control instruction. Details in
 | **M7 — Fixtures + Evaluation + starter KUs** | done | `knowledge/public/**` (14 KUs), `tests/fixtures/assessments/{safe,vulnerable,unknown}/`, `app/eval/metrics.py`, `scripts/evaluate.py`, JA retrieval (trigram) |
 | **M8 — Docs + hardening** | done | Security disclaimer (AC-15–18), KU `provenance` schema, `docs/{attribution,threat-model,architecture}.md`, `sbom.json`, `scripts/{secret_scan,generate_sbom,preflight}.py` |
 
-## Quickstart (M1)
+## Install
+
+Requires **Python 3.12+**. From PyPI (ships the default rules / knowledge /
+safe-test data, so `skos assess` works with no checkout):
+
+```bash
+pip install security-knowledge-os          # engine + CLI
+pip install "security-knowledge-os[api]"   # + the local FastAPI app
+skos assess your-agent.yaml                # your-agent.yaml is an input you write
+```
+
+## Quickstart (M1, from a source checkout)
 
 ```bash
 python3.12 -m venv .venv

{security_knowledge_os-0.1.0 → security_knowledge_os-0.2.0}/app/__init__.py

@@ -1,3 +1,3 @@
 """Security Knowledge OS - deterministic security assessment engine."""
 
-__version__ = "0.1.0"
+__version__ = "0.2.0"

security_knowledge_os-0.2.0/app/adapters/__init__.py

@@ -0,0 +1 @@
+"""Adapters: derive assessment inputs from real-world configuration."""