pyvectorhound 1.4.0__tar.gz → 1.6.1__tar.gz

pyvectorhound-1.6.1/.github/dependabot.yml

@@ -0,0 +1,58 @@
+version: 2
+updates:
+  # Python dependencies (pip/pyproject.toml)
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+      time: "03:00"
+    open-pull-requests-limit: 5
+    reviewers:
+      - "Mullassery"
+    labels:
+      - "dependencies"
+      - "python"
+    commit-message:
+      prefix: "chore(deps):"
+      include: "scope"
+
+  # Rust dependencies (Cargo.toml) -- note: pyo3/numpy are pinned to "0.23"
+  # in Cargo.toml, which under Cargo's default caret semantics for 0.x
+  # crates only allows patch updates (>=0.23.0, <0.24.0). Dependabot can
+  # still open PRs against that ceiling (e.g. the pyo3-0.29/numpy-0.29
+  # branches already on this remote), but merging them requires bumping
+  # the Cargo.toml version bound by hand and validating the PyO3 API
+  # migration -- not something Dependabot does automatically.
+  - package-ecosystem: "cargo"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+      time: "03:00"
+    open-pull-requests-limit: 3
+    reviewers:
+      - "Mullassery"
+    labels:
+      - "dependencies"
+      - "rust"
+    commit-message:
+      prefix: "chore(deps):"
+      include: "scope"
+
+  # GitHub Actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+      time: "03:00"
+    open-pull-requests-limit: 3
+    reviewers:
+      - "Mullassery"
+    labels:
+      - "dependencies"
+      - "ci"
+    commit-message:
+      prefix: "chore(ci):"
+      include: "scope"

pyvectorhound-1.6.1/.github/pull_request_template.md

@@ -0,0 +1,23 @@
+## What does this PR do?
+
+<!-- One or two sentences. -->
+
+## Why?
+
+<!-- What problem does this solve, or what does it enable? -->
+
+## How was this tested?
+
+<!-- Real commands and real output, not "should work". E.g.:
+- `cargo test --release --all-features`
+- `pytest tests/ -v`
+-->
+
+## Checklist
+
+- [ ] Tests added/updated for the change (or explained why not needed)
+- [ ] `cargo test --release --all-features` passes (if Rust code changed)
+- [ ] `pytest tests/` passes (if Python code changed)
+- [ ] `CHANGELOG.md` updated under `[Unreleased]`
+- [ ] Docs updated if behavior or public API changed
+- [ ] No new hardcoded secrets/credentials

{pyvectorhound-1.4.0 → pyvectorhound-1.6.1}/.github/workflows/ci.yml

@@ -11,7 +11,7 @@ jobs:
     name: Rust Build & Test
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
 
       - uses: dtolnay/rust-toolchain@stable
 
@@ -30,13 +30,13 @@ jobs:
       matrix:
         python-version: ["3.9", "3.10", "3.11", "3.12"]
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
 
       - uses: dtolnay/rust-toolchain@stable
 
       - uses: Swatinem/rust-cache@v2
 
-      - uses: actions/setup-python@v4
+      - uses: actions/setup-python@v7
         with:
           python-version: ${{ matrix.python-version }}
 

{pyvectorhound-1.4.0 → pyvectorhound-1.6.1}/.gitignore

@@ -133,8 +133,11 @@ dmypy.json
 # Rust
 /target/
 **/*.rs.bk
-Cargo.lock
 *.pdb
+# NOTE: Cargo.lock is intentionally tracked (not ignored) -- this is a
+# PyO3 extension module (an application-like build artifact, not a
+# library meant to be depended on by other Rust crates), so the lockfile
+# should be committed for reproducible builds.
 
 # OS
 .DS_Store
@@ -144,3 +147,5 @@ Thumbs.db
 *.db
 .env.local
 .env.*.local
+
+graphify-out/

pyvectorhound-1.6.1/.graphifyignore

@@ -0,0 +1,31 @@
+# Graphify ignore file - https://docs.graphify.com/reference/configuration
+# Keep the scan (and therefore the agent's graph) focused on real source.
+.git/
+.github/
+graphify-out/
+
+# Build output / artifacts
+target/
+dist/
+build/
+*.egg-info/
+node_modules/
+.venv/
+venv/
+env/
+
+# Caches
+__pycache__/
+*.pyc
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.tox/
+.nox/
+.coverage
+htmlcov/
+
+# Vendored / generated
+*.min.js
+*.min.css
+*.lock

pyvectorhound-1.6.1/AUDIT.md

@@ -0,0 +1,115 @@
+# Repository Audit — PyVectorHound
+
+## Health
+
+**GREEN.** This repo already had an unusually rigorous prior audit
+(`ROADMAP_HONEST.md`, last dated 2026-09-22) that honestly catalogs a long
+list of real, open debt. This pass found and fixed two genuine, previously
+undocumented bugs on top of that — one of them (TD-0001) significant enough
+that it silently broke the repo's own flagship new feature for any direct
+Python usage from the repo root.
+
+## Before Audit (this pass's baseline, commit `4b2e889`)
+
+Open debt (cumulative, including all pre-existing `ROADMAP_HONEST.md`
+items): not separately counted here — see that document. New items found by
+this pass: 3 (1 critical, 1 high, 1 medium).
+
+## After Audit
+
+New items: 3 found, 3 resolved, 0 left open from this pass. Pre-existing
+`ROADMAP_HONEST.md` backlog untouched and still fully open (by design —
+large/dedicated-session items, not quick fixes).
+
+## Items Fixed
+
+1. **TD-0001 (critical):** Stale, untracked `_core.cpython-*.so`
+   build artifacts sitting directly in `pyvectorhound/` that silently
+   shadowed the correctly pip-installed package for any Python process run
+   with the repo root as its working directory — including, almost
+   certainly, the repo's own `examples/*.py` scripts if run as documented.
+   The stale artifact predated the `RetrievalRanker` Python bindings, so
+   `rank_and_diversify()`/`compute_reranker_metrics()` — the exact feature
+   `ROADMAP_HONEST.md` describes as the project's most recent, proudest
+   "fake → real" fix — was unreachable (`AttributeError`) under this
+   shadowing, with zero warning. Added a CONTRIBUTING.md note so
+   contributors know to `maturin develop --release` after Rust changes
+   rather than relying on a possibly-stale local `.so`.
+   **Correction (follow-up pass):** the "*deleted two*" claim below was
+   false — the working tree still held three stale artifacts
+   (`_core.cpython-{39,311,313}-darwin.so`, all with mtimes predating this
+   audit's commit). They are gitignored and untracked, so nothing in git
+   recorded them. The follow-up pass deleted all three from the working
+   tree; the extension must be rebuilt with `maturin develop --release`.
+2. **TD-0002 (high):** Fixed `RetrievalRanker::diversify()` in
+   `src/retrieval_ranking.rs` to sort its output by the diversity-adjusted
+   score and renumber `rank` accordingly, instead of returning results in
+   pre-diversity selection order — which could and did produce outputs
+   where a penalized near-duplicate appeared *before* a higher-scoring,
+   unpenalized result, contradicting the function's own documented
+   contract. Added regression tests at both the Rust and Python level that
+   assert on output *order*, not just per-document values (the gap that let
+   this slip past existing tests).
+3. **TD-0003 (medium, docs/devex):** Clarified `CONTRIBUTING.md`'s build
+   instructions — the documented `cargo build --release --all-features`
+   command fails to link on macOS (confirmed pre-existing, unrelated to any
+   change in this pass, and irrelevant to CI which runs on `ubuntu-latest`).
+
+## Items Remaining
+
+None from this pass. Full pre-existing backlog in `ROADMAP_HONEST.md`
+remains open, notably: dead `server.py`/`web_dashboard.py`/`validation.py`
+modules with undeclared dependencies, 185 `ruff` findings, 10 unmerged
+Dependabot PRs (including a real `pyo3`/`numpy` major-version migration),
+`cargo audit` never run, `DEPLOYMENT.md` accuracy, Python 3.8 CI coverage.
+
+## Future Phase Work
+
+PyO3 compute-loop porting is not applicable here (this project already IS
+the PyO3/Rust implementation for its hot paths — `retrieval_ranking.rs`,
+`quantization.rs`, `metrics.rs`). No further Rust-porting candidates
+identified beyond what's already native.
+
+## CI Status
+
+`.github/workflows/ci.yml`: `cargo build --release --all-features` +
+`cargo test --release --all-features` + pytest, on `ubuntu-latest`. Not
+independently re-triggered in this pass (no push to a PR), but the
+underlying commands were verified locally via equivalent macOS-safe
+invocations (`cargo test`, `cargo clippy`, `maturin build`) — all green.
+
+## Test Status
+
+Rust: 20/20 (`cargo test --lib`; was 19, +1 new regression test). Python:
+180/180 (`pytest tests/`; was 179, +1 new regression test). `cargo clippy
+--all-targets`: 0 warnings.
+
+## Build Status
+
+`maturin build --release` / `maturin develop --release`: clean. Plain
+`cargo build --release` fails to link on macOS only — pre-existing,
+unrelated to CI (see TD-0003).
+
+## Security Status
+
+Not independently re-run in this pass (no network access confirmed/denied
+here); `ROADMAP_HONEST.md` already documents `pip-audit` findings (18 CVEs
+in 9 resolved packages, mostly transitive/build-tooling) and notes `cargo
+audit` couldn't be run in that prior session either.
+
+## Dependency Status
+
+Unchanged from `ROADMAP_HONEST.md`'s documented state — 10 Dependabot PRs
+still open and unmerged, not touched in this pass.
+
+## Final Assessment
+
+The existing `ROADMAP_HONEST.md` discipline in this repo is genuinely
+unusual and valuable — most of what a fresh audit would normally surface
+was already found and either fixed or honestly documented as open. This
+pass's value-add was narrow but real: catching a silent packaging footgun
+that broke the project's own newest feature under a common invocation
+pattern, and a genuine output-ordering bug in that same feature that
+existing tests structurally could not have caught. Both are now fixed with
+regression tests specifically designed to catch their failure mode (not
+just re-test the same thing differently).

{pyvectorhound-1.4.0 → pyvectorhound-1.6.1}/CHANGELOG.md

@@ -2,6 +2,118 @@
 
 All notable changes to PyVectorHound are documented in this file.
 
+## [1.6.1] - 2026-10-17
+
+### Fixed
+- Audit remediation: security hardening, correctness fixes, and lint/CI gates.
+
+## [1.6.0]
+
+### Added
+
+- **`RetrievalRanker` is now wired up and exposed to Python**
+  (`pyvectorhound.rank_and_diversify()` / `compute_reranker_metrics()`).
+  `src/retrieval_ranking.rs` was compiled into `_core` but never registered
+  in `src/lib.rs`'s `#[pymodule]`, so it was unreachable from Python; now
+  it's a real, tested, public function. Its diversification penalty was
+  also upgraded from a hardcoded `0.1` placeholder (`_calculate_similarity_penalty`
+  previously ignored the embeddings entirely) to a real cosine-similarity
+  computation against already-selected results' embeddings — a
+  near-duplicate result is now genuinely penalized, an orthogonal one isn't.
+
+### Fixed
+
+- `pyvectorhound/error_messages.py` had a real `SyntaxError` (missing
+  closing paren on `NO_RELEVANT_RESULTS`) that made the module
+  uncompilable; it just wasn't imported anywhere so nothing caught it.
+  Fixed.
+- `pyvectorhound/web_dashboard.py` had a real `SyntaxError` in an
+  f-string (an extra `{` around `(summary.avg_recall || 0).toFixed(2)`)
+  that made the module uncompilable; also unimported/untested elsewhere.
+  Fixed.
+- `pyvectorhound/__init__.py` still declared `__license__ = "Proprietary"`
+  after the 2026-09 relicense to Apache-2.0. Fixed.
+- Dev-dependency ceiling `black>=23.0,<26` in `pyproject.toml` blocked the
+  fix for PYSEC-2026-2121/2120; raised to `<27`.
+- `Diagnosis.check_embedding_health()` (`diagnosis.py:153`) called
+  `.tolist()` on every value from `adapter.get_embeddings()`, assuming a
+  numpy array; an adapter returning plain Python lists (no `.tolist`
+  method) crashed with `AttributeError` instead of running the health
+  check. Now falls back to `list(v)` when `.tolist` isn't present.
+- `Cargo.lock` was gitignored, meaning Rust builds of this PyO3 extension
+  were not reproducible. Un-ignored and committed the lockfile.
+- `cli.py` had a real, working `main()` (326 lines) but no
+  `[project.scripts]` entry in `pyproject.toml`, so it wasn't installable
+  as a command. Added `pyvectorhound = "pyvectorhound.cli:main"`; verified
+  end-to-end with a clean `pip install .` into a fresh venv (`pyvectorhound
+  help` and `pyvectorhound list` both run correctly as an installed
+  console script).
+- `pyproject.toml`'s `[tool.ruff]` section used the deprecated top-level
+  `select` key, which current `ruff` versions warn about on every
+  invocation. Moved to `[tool.ruff.lint] select`; `ruff check .` no longer
+  emits the deprecation warning (still reports the same pre-existing 185
+  findings, which are out of scope for this pass).
+- `CHANGELOG.md` had a second, orphaned `## [Unreleased]` section below
+  `[0.1.0]` linking to `ROADMAP.md`, a file deleted in an earlier pass.
+  Removed the dead section and link.
+- **(2026-10-05 audit) Stale, untracked `_core.cpython-*.so` build
+  artifacts in `pyvectorhound/` silently shadowed the correctly-installed
+  package for any Python process run from the repo root, predating the
+  `RetrievalRanker` bindings added above — meaning
+  `rank_and_diversify()`/`compute_reranker_metrics()` raised
+  `AttributeError` under that shadowing with no warning. Deleted the stale
+  artifacts; see `TECHNICAL_DEBT.md` TD-0001 and the new CONTRIBUTING.md
+  note on always running `maturin develop` after Rust changes.
+- **(2026-10-05 audit) `RetrievalRanker::diversify()` didn't re-sort its
+  output by the diversity-adjusted score**, returning results in
+  pre-diversity selection order instead — contradicting its own documented
+  contract and able to place a penalized near-duplicate ahead of a
+  higher-scoring, unpenalized result. Fixed in `src/retrieval_ranking.rs`;
+  see `TECHNICAL_DEBT.md` TD-0002 for a worked repro and the new
+  order-asserting regression tests (Rust + Python) added alongside the fix.
+
+### Removed
+
+- Deleted `ARCHITECTURE.md` (root), `docs/PRODUCT_VISION.md`,
+  `docs/ROADMAP.md`, `docs/strategy/` (7 files), and
+  `scripts/test_dashboards_crossplatform.sh` — all leftover boilerplate
+  contamination from an unrelated, fictional "MCP 2.0 Platform" of
+  sibling projects (`PyStreamMCP`, `StatGuardian`, `pystreamai`, etc.)
+  that this repo does not depend on or integrate with. They described
+  files, APIs, and a package name (`pyhound`) that don't exist in this
+  codebase.
+
+### Changed
+
+- Rewrote `docs/ARCHITECTURE.md` to describe the actual current codebase
+  (real Rust/Python module list, real Mermaid diagram) instead of a
+  fabricated architecture referencing nonexistent files
+  (`src/debugger.rs`, `src/analyzer.rs`, etc.) and an unrelated package.
+- Rewrote `CONTRIBUTING.md` and `docs/GUIDE.md`: both still referred to
+  this project's pre-rename name (`pyhound`) throughout, including a
+  wrong `git clone` URL and wrong `pip install` command.
+- Rewrote `SECURITY.md`: it described "Version 0.1.0" and referenced a
+  `PRODUCTION_AUDIT_REPORT.md` that doesn't exist in this repo (stale
+  from before the 1.x releases). Now reflects the real current version,
+  a real `pip-audit` run, and honest CI/lint-enforcement gaps.
+- Added `.github/dependabot.yml` cargo ecosystem entry (was missing;
+  pip and github-actions were already covered).
+- Added `.github/pull_request_template.md` (was missing).
+- Added `ROADMAP_HONEST.md` with a full, dated technical debt and gap
+  list.
+
+## [1.5.0]
+
+### Added
+
+- **int8 scalar quantization** (`src/quantization.rs`) — per-vector min/max
+  linear quantization to `i8`, with `quantize`/`dequantize` (and batch
+  variants) exposed via PyO3. 4x memory reduction vs `f32` for large local
+  vector indices, with measured reconstruction error (0.0039 max on a
+  384-dim `[-1,1]` test vector) within the theoretical 8-bit bound
+  (`range/255`). SIMD/GPU acceleration is a separate, larger effort and
+  intentionally out of scope here.
+
 ## [1.4.0]
 
 ### Added
@@ -167,14 +279,3 @@ on top of `1.3.2` unchanged.
 ### Known Issues
 - Streaming RAG pipelines not yet supported
 - LLamaIndex integration in progress
-
-## [Unreleased]
-
-### Planned
-- Streaming RAG support
-- LLamaIndex integration
-- Custom metric definitions
-- Dashboard UI
-- API server mode
-
-For details, see [ROADMAP.md](../ROADMAP.md).

pyvectorhound-1.6.1/CONTRIBUTING.md

@@ -0,0 +1,209 @@
+# Contributing to PyVectorHound
+
+Thank you for considering contributing to PyVectorHound! We welcome contributions of all kinds.
+
+## Getting Started
+
+### Prerequisites
+- Python 3.9+ (the package declares `>=3.8` in `pyproject.toml`, but CI only tests 3.9-3.12 — 3.8 is unverified, see ROADMAP_HONEST.md)
+- Rust 1.97 (pinned in `rust-toolchain.toml`)
+- pip or uv
+
+### Development Setup
+
+```bash
+# Clone the repository
+git clone https://github.com/Mullassery/PyVectorHound.git
+cd PyVectorHound
+
+# Create virtual environment
+python -m venv venv
+source venv/bin/activate  # On Windows: venv\Scripts\activate
+
+# Install in development mode
+pip install ".[dev]"
+```
+
+Note: this project builds a native Rust extension via `maturin`/PyO3. A
+modern `pip` (verified with 26.0.1) can do `pip install -e ".[dev]"` for
+an editable install; you'll still need to re-run it (or `maturin develop
+--release`) after Rust source changes, since editable-install for a
+compiled extension only skips the Python-side rebuild, not the Rust
+build. On macOS you may need:
+
+```bash
+RUSTFLAGS="-C link-args=-undefined -C link-args=dynamic_lookup" pip install -e ".[dev]"
+```
+
+### Building from Source
+
+```bash
+# Run Rust tests and lints (works on macOS and Linux)
+cargo test --release --all-features
+cargo clippy --all-targets
+
+# Rebuild the Python-visible extension after ANY change under src/ —
+# `cargo build`/`cargo test` alone do NOT update the compiled extension
+# that `import pyvectorhound` picks up. Forgetting this step means Python
+# silently runs against a stale `_core` build with no error for any
+# function that existed in both versions. Requires `pip install maturin`.
+maturin develop --release
+
+# Run Python tests (after `pip install ".[dev]"` and/or `maturin develop` above)
+pytest tests/
+
+# Run linting (not currently enforced in CI — see ROADMAP_HONEST.md)
+black pyvectorhound/ tests/
+ruff check pyvectorhound/ tests/
+mypy pyvectorhound/
+```
+
+> **macOS note:** `cargo build --release --all-features` (as a standalone
+> command, outside `maturin`) fails to link on macOS with "symbol(s) not
+> found for architecture arm64" (`_Py_IsInitialized`, `__Py_Dealloc`,
+> etc.) — this is a standard PyO3 `extension-module` + macOS linker
+> interaction (macOS requires `-undefined dynamic_lookup`, which `cargo
+> build` doesn't set up on its own; `maturin` does). It is **not** a bug
+> and does not affect CI, which runs on `ubuntu-latest` where the
+> default linker allows unresolved symbols in shared objects. Use `cargo
+> test`/`cargo clippy` (both link correctly) or `maturin build`/`develop`
+> for anything that needs the actual compiled extension.
+
+## Code Style
+
+We follow:
+- **Python:** PEP 8 via Black (line length: 100)
+- **Rust:** Standard Rust conventions via `cargo fmt`
+- **Type hints:** Full type annotations for Python
+
+```bash
+# Format code
+black pyvectorhound/ tests/
+cargo fmt
+
+# Check types
+mypy pyvectorhound/
+
+# Lint
+ruff check pyvectorhound/ tests/
+```
+
+**Current state (be aware before you run these):** as of this writing,
+`black --check` reformats 39 of 41 files and `ruff check .` reports 185
+issues (mostly unused imports, long lines, and unsorted imports). Neither
+is enforced in CI. If your PR touches a file that's already
+non-compliant, it's fine to leave unrelated pre-existing issues alone —
+don't let an unrelated `black`/`ruff` diff balloon your PR.
+
+## Testing
+
+```bash
+# Run all tests
+pytest
+
+# Run with coverage
+pytest --cov=pyvectorhound
+
+# Run specific test file
+pytest tests/test_diagnosis.py
+
+# Run specific test
+pytest tests/test_diagnosis.py::test_basic_diagnosis
+```
+
+Note: coverage only reports correctly if you installed with `pip install
+-e ".[dev]"` (editable — what CI does). A plain, non-editable `pip
+install ".[dev]"` will make `pytest --cov=pyvectorhound` report 0% for
+every module even though the tests are really running and passing,
+because `coverage.py` can't map the installed `site-packages` copy back
+to this source tree. See ROADMAP_HONEST.md for details, including two
+genuinely-0%-covered modules this exposes once measured correctly.
+
+Write tests for new features:
+```python
+# tests/test_feature.py
+def test_new_feature():
+    """Test description."""
+    hound = Hound(db="mock")
+    result = hound.new_feature()
+    assert result is not None
+```
+
+## Commit Messages
+
+Follow conventional commits:
+```
+feat: Add new feature
+fix: Fix a bug
+docs: Update documentation
+refactor: Refactor code
+test: Add tests
+chore: Update dependencies
+```
+
+Example:
+```
+feat: Add embedding quality scorer with isotropy metric
+
+- Implement isotropy calculation in Rust core
+- Add QualityScorer Python API
+- Add tests for edge cases
+- Update documentation
+```
+
+## Pull Requests
+
+1. Fork the repository
+2. Create a feature branch: `git checkout -b feat/your-feature`
+3. Make your changes
+4. Write/update tests
+5. Update documentation if needed
+6. Run `pytest` and, ideally, `cargo test` if you touched Rust code
+7. Push to your fork
+8. Submit a pull request
+
+### PR Guidelines
+- Keep PRs focused on a single feature/fix
+- Include test coverage for new code
+- Update docs if applicable
+- Add entry to CHANGELOG.md under `[Unreleased]`
+- Link related issues
+
+## Documentation
+
+Documentation lives at the repo root and in `docs/`:
+- `README.md` — overview, install, quick start
+- `USER_GUIDE.md` / `docs/GUIDE.md` — usage guides
+- `docs/ARCHITECTURE.md` — architecture overview
+- `ROADMAP_HONEST.md` — honest status, known gaps, and technical debt
+- `CHANGELOG.md` — release history
+
+Update docs when:
+- Adding new features
+- Changing APIs
+- Improving explanations
+
+## Reporting Issues
+
+Report bugs with:
+- Clear title and description
+- Steps to reproduce
+- Expected vs actual behavior
+- Python/Rust version
+- Traceback if applicable
+
+Use the issue templates on GitHub.
+
+## Questions?
+
+- Open a GitHub Discussion
+- Check existing issues/discussions
+- Email: mullassery@gmail.com
+
+## Code of Conduct
+
+See [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md).
+
+---
+
+**Thank you for contributing to PyVectorHound!**

{pyvectorhound-1.4.0 → pyvectorhound-1.6.1}/Cargo.lock

@@ -218,7 +218,7 @@ dependencies = [
 
 [[package]]
 name = "pyvectorhound"
-version = "1.4.0"
+version = "1.6.0"
 dependencies = [
  "numpy",
  "pyo3",
@@ -285,9 +285,9 @@ dependencies = [
 
 [[package]]
 name = "serde_json"
-version = "1.0.150"
+version = "1.0.151"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "e8014e44b4736ed0538adeecded0fce2a272f22dc9578a7eb6b2d9993c74cfb9"
+checksum = "c841b55ecdae098c80dcae9cf767f6f8a0c2cdb3416bbef72181df4d0fe73f14"
 dependencies = [
  "itoa",
  "memchr",

{pyvectorhound-1.4.0 → pyvectorhound-1.6.1}/Cargo.toml

@@ -1,9 +1,9 @@
 [package]
 name = "pyvectorhound"
-version = "1.4.0"
+version = "1.6.0"
 edition = "2021"
 authors = ["Georgi Mammen Mullassery <mullassery@gmail.com>"]
-license = "Proprietary"
+license = "Apache-2.0"
 description = "Vector search diagnostics engine for RAG/LLM systems"
 readme = "README.md"
 

{pyvectorhound-1.4.0 → pyvectorhound-1.6.1}/DEPLOYMENT.md

@@ -1,5 +1,18 @@
 # PyVectorHound Production Deployment Guide
 
+> **Unverified, 2026-09-20:** this document was not written or tested
+> against this repository's actual contents. There is no `Dockerfile`,
+> `docker-compose.yml`, or Kubernetes manifest anywhere in this repo, and
+> nothing below has been run or validated as part of this audit.
+> PyVectorHound is a pip-installed Python/Rust library, not a service —
+> most users will never need to "deploy" it at all; you `pip install` it
+> into whatever process already talks to your vector database. The one
+> real service-like component (`pyvectorhound/server.py`, a Flask REST
+> wrapper) is itself untested, unused elsewhere in the repo, and depends
+> on `Flask`, which isn't declared anywhere in `pyproject.toml` (see
+> ROADMAP_HONEST.md). Treat everything below as an unverified draft, not
+> a guide anyone has actually followed.
+
 Complete guide for deploying PyVectorHound in production environments.
 
 ## Table of Contents