vilopa 0.0.1__tar.gz

vilopa-0.0.1/.github/workflows/ci.yml

@@ -0,0 +1,60 @@
+name: ci
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+
+jobs:
+  check:
+    name: lint, types, unit
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7  # v10.2.0
+      - run: uv sync --locked
+      - run: uv run ruff check .
+      - run: uv run ruff format --check .
+      - run: uv run mypy
+      - run: uv run pytest -m "not db"
+
+  seed:
+    name: demo shop seed (Postgres 16)
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    services:
+      postgres:
+        image: postgres:16
+        env:
+          POSTGRES_USER: mita
+          POSTGRES_PASSWORD: mita
+          POSTGRES_DB: bharat_bazaar
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd "pg_isready -U mita -d bharat_bazaar"
+          --health-interval 2s --health-timeout 5s --health-retries 20
+    env:
+      MITA_APP_PG_DSN: postgresql://mita:mita@localhost:5432/bharat_bazaar
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7  # v10.2.0
+      - run: uv sync --locked
+      - run: uv run python examples/bharat-bazaar/seed.py
+      - run: uv run pytest -m db
+      - name: lint the demo data map through the GitHub Action
+        uses: ./
+        with:
+          datamap: examples/bharat-bazaar/datamap.yaml

vilopa-0.0.1/.github/workflows/release.yml

@@ -0,0 +1,50 @@
+name: release
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    name: build and check
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7  # v10.2.0
+      - run: uv sync --locked
+      - run: uv run ruff check .
+      - run: uv run mypy
+      - run: uv run pytest -m "not db"
+      - name: tag matches the package version
+        env:
+          TAG: ${{ github.ref_name }}
+        run: test "v$(uv version --short)" = "$TAG"
+      - run: uv build
+      - uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9  # v7.0.2
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    # Trusted publishing: PyPI accepts the job's OIDC token, so no API token is stored.
+    environment:
+      name: pypi
+      url: https://pypi.org/p/vilopa
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333  # v8.0.2
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@7245906fb61fa33a13554f9d5fb856fe61758086  # v1.14.3

vilopa-0.0.1/.gitignore

@@ -0,0 +1,10 @@
+.venv/
+__pycache__/
+*.py[cod]
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+dist/
+build/
+.env
+.env.*

vilopa-0.0.1/.python-version

@@ -0,0 +1 @@
+3.12

vilopa-0.0.1/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

vilopa-0.0.1/Makefile

@@ -0,0 +1,36 @@
+export MITA_APP_PG_DSN ?= postgresql://mita:mita@127.0.0.1:55432/bharat_bazaar
+COMPOSE := docker compose -f deploy/compose.dev.yml
+
+.PHONY: dev down seed test-fast test-db lint fmt types schema check
+
+dev:  ## install dependencies and start Postgres
+	uv sync
+	$(COMPOSE) up -d --wait
+
+down:
+	$(COMPOSE) down
+
+seed:  ## load the demo shop into the dev database
+	uv run python examples/bharat-bazaar/seed.py
+
+test-fast:  ## unit tests, no database
+	uv run pytest -m "not db"
+
+test-db:  ## integration tests against the dev database
+	uv run pytest -m db
+
+lint:
+	uv run ruff check .
+	uv run ruff format --check .
+
+fmt:
+	uv run ruff format .
+	uv run ruff check --fix .
+
+types:
+	uv run mypy
+
+schema:  ## regenerate the committed data map JSON Schema
+	uv run mita datamap schema > schemas/datamap.schema.json
+
+check: lint types test-fast

vilopa-0.0.1/PKG-INFO

@@ -0,0 +1,180 @@
+Metadata-Version: 2.5
+Name: vilopa
+Version: 0.0.1
+Summary: Execute and verify data-erasure and access requests across your databases, storage and SaaS tools. Self-hosted, DPDP-aware.
+Project-URL: Homepage, https://github.com/hrithiknl17/mita
+Project-URL: Issues, https://github.com/hrithiknl17/mita/issues
+Author: Hrithik
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: data-erasure,dpdp,gdpr,postgres,privacy-engineering
+Requires-Python: >=3.12
+Requires-Dist: psycopg[binary]>=3.2
+Requires-Dist: pydantic>=2.9
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: typer>=0.12
+Description-Content-Type: text/markdown
+
+# mita
+
+Delete a person's data from every system you mapped, prove it, and hit the deadline.
+Self-hosted. DPDP-aware. Not legal advice.
+
+> **Status: pre-alpha.** mita does not delete anything yet. What exists today: the data map
+> format with a validator, `mita scan` and `mita lint` for finding personal data your map
+> misses, and a demo shop database seeded with canary data for testing erasure. Follow the
+> [roadmap](#roadmap).
+
+## Install
+
+```sh
+pip install vilopa    # or: uv tool install vilopa
+```
+
+The package is published as `vilopa`; the command and the import are `mita`.
+
+```sh
+mita --version
+```
+
+## Why this exists
+
+- From May 2027, Indian companies must answer erasure and access requests within a fixed
+  deadline and delete personal data once its purpose is served (DPDP Act and Rules).
+- Personal data spreads across your database, file storage and SaaS tools. A hand-written
+  delete script does not verify, does not track deadlines, and silently breaks when someone
+  adds a new column holding a phone number.
+
+## What it is not
+
+- Not a consent manager (see [tsi-dpdp-cms](https://github.com/tsi-coop/tsi-dpdp-cms)).
+- Not legal advice, and not "compliance in a box". Companies are compliant; tools are not.
+- It cannot see copies you did not map, and it cannot rewrite old backups.
+
+## The data map
+
+You describe where personal data lives in a YAML file kept in your repo and reviewed in PRs:
+
+```yaml
+principal:
+  root: app_pg.public.customers
+  keys:
+    email: { column: email, normalize: email }
+
+tables:
+  app_pg.public.invoices:
+    erase: retain
+    retain:
+      reason: Tax invoices must be kept as issued.
+      period: P8Y
+      from_column: issued_at
+```
+
+See the full demo map in [`examples/bharat-bazaar/datamap.yaml`](examples/bharat-bazaar/datamap.yaml)
+and the JSON Schema in [`schemas/datamap.schema.json`](schemas/datamap.schema.json). Editors with the
+YAML language server get completion and validation from it.
+
+```console
+$ uv run mita datamap validate examples/bharat-bazaar/datamap.yaml
+examples/bharat-bazaar/datamap.yaml: ok (9 tables, 1 connector(s))
+```
+
+## Finding personal data: `mita scan` and `mita lint`
+
+`mita scan` lists the columns of a live Postgres database that look like personal data, from
+their names, types and a sample of their values. It recognises Indian identifiers by shape:
+mobile numbers in any common format, PAN, GSTIN, Aadhaar (with its check digit), UPI IDs and
+PIN codes, as well as emails, IP addresses, and free text with emails or phone numbers inside.
+
+```console
+$ DATABASE_URL=postgresql://... uv run mita scan --connector app_pg
+COLUMN                                       CATEGORY     CONFIDENCE  WHY
+app_pg.public.customers.email                email        high        name suggests email; 200/200 sampled values look like email
+app_pg.public.customers.pan                  pan          high        name suggests pan; 94/94 sampled values look like pan
+app_pg.public.events.properties              free_text    medium      36/200 sampled values contain an email address or phone number
+app_pg.public.events.ip                      ip_address   high        column type is inet
+app_pg.public.products.name                  name         low         name suggests name
+...
+71 columns scanned, 22 look like personal data (14 high, 6 medium, 2 low)
+```
+
+`mita lint` fails when the database and the map disagree: a column that looks like personal
+data at medium confidence or above is not in the map, or the map names a table or column that
+no longer exists. Columns you reviewed and marked `pii: none` never fail the lint.
+
+```console
+$ uv run mita lint examples/bharat-bazaar/datamap.yaml
+examples/bharat-bazaar/datamap.yaml: error: app_pg.public.customers.alt_mobile: looks like phone (high: name suggests phone); not in the data map
+examples/bharat-bazaar/datamap.yaml: app_pg: 1 error(s), 0 warning(s)
+```
+
+Both connect read-only with a statement timeout, and never print, log or store a sampled
+value: reports carry categories, confidences and counts only. Sampling reads the first rows a
+table returns, not a random sample; `--sample-rows 0` classifies by name and type alone, which
+is what you want against a freshly migrated, empty CI database.
+
+### In CI
+
+Run your migrations against a throwaway database, then lint the map in the same job:
+
+```yaml
+- uses: hrithiknl17/mita@v0.0.1  # pin a commit SHA in real use
+  env:
+    MITA_APP_PG_DSN: postgresql://app:app@localhost:5432/app  # the map's dsn_env
+  with:
+    datamap: privacy/datamap.yaml
+    sample-rows: 0
+```
+
+## Development
+
+Needs [uv](https://docs.astral.sh/uv/) and Docker.
+
+```sh
+make dev        # uv sync + start Postgres 16 on 127.0.0.1:55432
+make seed       # load the Bharat Bazaar demo shop
+make check      # ruff, mypy --strict, unit tests
+make test-db    # integration tests against the dev database
+```
+
+No `make` (for example on Windows)? The same steps:
+
+```sh
+uv sync
+docker compose -f deploy/compose.dev.yml up -d --wait
+uv run python examples/bharat-bazaar/seed.py
+uv run ruff check . && uv run mypy && uv run pytest -m "not db"
+MITA_APP_PG_DSN=postgresql://mita:mita@127.0.0.1:55432/bharat_bazaar uv run pytest -m db
+```
+
+### The demo shop and its canaries
+
+`examples/bharat-bazaar` is a small Indian e-commerce schema with shapes that make erasure
+hard on purpose: a self-referencing FK, orders kept for accounting, tax invoices that must be
+retained, guest support tickets linked only by email, an analytics table with no foreign key,
+and phone numbers inside free text in four different formats.
+
+Every seeded customer carries a unique canary token in their personal fields. The erasure
+tests will check two things: after erasing one customer, their token appears nowhere
+(**canary**), and every other customer's rows are unchanged (**bystander**). The seed is
+deterministic, so failures reproduce.
+
+## Architecture decisions
+
+- [0001 Postgres is the job queue](docs/adr/0001-postgres-as-the-job-queue.md)
+- [0002 Principals are stored as keyed hashes](docs/adr/0002-hmac-principals.md)
+- [0003 No language model in the deletion path](docs/adr/0003-no-llm-in-the-deletion-path.md)
+
+## Roadmap
+
+1. ~~**`mita scan` and `mita lint`**~~ (done): find PII-looking columns in a live Postgres
+   schema, and fail CI when a migration adds one the data map does not cover. Ships as a
+   GitHub Action.
+2. **`mita plan`**: resolve a person across tables through foreign keys and declared
+   relations, order the deletes, and refuse plans that touch too many rows.
+3. **`mita erase` / `mita access`**: execute, verify, and write an evidence record.
+4. **Service**: request intake, approvals, deadlines, retention sweeps, connectors.
+
+## License
+
+[Apache-2.0](LICENSE)