agent-sanitizer 2.0.0__tar.gz

agent_sanitizer-2.0.0/.gitignore

@@ -0,0 +1,61 @@
+# Claude Code worktree scaffolding
+.worktrees/
+.claude/worktrees/
+
+# Dependencies
+node_modules
+.pnpm-store/
+pnpm-lock.yaml
+
+# Build outputs
+dist/
+build/
+out/
+types/
+
+# Environment files
+.env
+.env.local
+.env.*.local
+
+# IDE
+.idea/
+.vscode/
+*.swp
+*.swo
+
+# Claude Code local settings (written by SessionStart hook in web sessions)
+.claude/settings.local.json
+
+# Claude Code personal notes (recurring nitpicks / review feedback, never committed)
+CLAUDE.local.md
+.claude/CLAUDE.local.md
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Logs
+*.log
+npm-debug.log*
+pnpm-debug.log*
+
+# Coverage
+coverage/
+
+# Python
+__pycache__/
+*.pyc
+.venv/
+.uv/
+*.egg-info/
+
+# Generated: the self-contained CLI bundled into the Python wheel at build time
+# (see scripts/bundle-python-cli.mjs). A build artifact from src/, never committed.
+python/agent_sanitizer/_bundled/
+
+# Stryker mutation testing
+.stryker-tmp/
+reports/mutation/
+reports/stryker-incremental.json
+stryker.shard.json

agent_sanitizer-2.0.0/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 2026 Alexander Turner
+
+   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.

agent_sanitizer-2.0.0/PKG-INFO

@@ -0,0 +1,130 @@
+Metadata-Version: 2.4
+Name: agent-sanitizer
+Version: 2.0.0
+Summary: Python client for agent-sanitizer: a thin bridge to the Node.js CLI for byte-identical sanitization verdicts.
+Project-URL: Homepage, https://github.com/AlexanderMattTurner/agent-sanitizer
+Project-URL: Repository, https://github.com/AlexanderMattTurner/agent-sanitizer
+Project-URL: Issues, https://github.com/AlexanderMattTurner/agent-sanitizer/issues
+License-Expression: Apache-2.0
+Keywords: ansi,prompt-injection,sanitizer,security,unicode
+Classifier: License :: OSI Approved :: Apache Software License
+Requires-Python: >=3.10
+Provides-Extra: secrets
+Requires-Dist: detect-secrets>=1.5.0; extra == 'secrets'
+Description-Content-Type: text/markdown
+
+# agent-sanitizer (Python client)
+
+A thin Python bridge to the [`agent-sanitizer`](https://github.com/AlexanderMattTurner/agent-sanitizer)
+Node.js CLI. The sanitization logic has a single source of truth — the
+JavaScript in `src/` — so this package shells out to the CLI rather than
+re-implementing it, giving a Python pipeline byte-identical verdicts with no
+second implementation to keep in sync.
+
+## Requirements
+
+- **Node.js (>= 22) on `PATH`.** The sanitizer is JavaScript; something has to
+  run it. There is deliberately no pure-Python fallback.
+
+That's it — `pip install agent-sanitizer` and, with Node available, you're
+ready to go. The wheel ships a self-contained, single-file build of the CLI
+(the `src/` logic and its npm dependencies bundled into one `.mjs` at release
+time), so there is no separate JavaScript checkout to clone and no environment
+variable to set. The bundle is a versioned build artifact from `src/`, not a
+hand-maintained port, so it can't drift from the JS.
+
+### Optional: point at your own JS checkout
+
+Set `AGENT_SANITIZER_CLI` to a checkout's `bin/sanitize-cli.mjs` to override the
+bundled CLI (e.g. to run against unreleased `src/` changes). When the module is
+imported directly from a repo checkout, the source CLI is found automatically.
+
+## Usage
+
+```python
+from agent_sanitizer import sanitize
+
+result = sanitize("untrusted text", html=True)
+print(result.cleaned, result.found, result.warnings)
+```
+
+See the package docstring for the full set of entry points (`sanitize_text`,
+`classify_prompt`, `scan_instruction_files`, `clean_file`, and the long-lived
+`Sanitizer` worker).
+
+## Secret redaction (`[secrets]` extra)
+
+The base install is dependency-free. The optional `secrets` extra adds a
+pure-Python secret-redaction engine under `agent_sanitizer.secrets` —
+detect-secrets plus custom detectors, benign-value skipping, cross-line
+reassembly, PEM collapse, and exact-match redaction of caller-supplied env-var
+values. Unlike the sanitizer above it needs **no Node.js**; its only dependency
+is `detect-secrets`, pulled in by the extra:
+
+```bash
+pip install "agent-sanitizer[secrets]"
+```
+
+Every detect-secrets import lives inside this subpackage, so a plain
+`import agent_sanitizer` never touches it. The engine shares the parent
+package's invisible-character SSOT (`agent_sanitizer.invisible`) rather
+than forking it — a fork would be a silent security regression.
+
+### In-process
+
+```python
+from agent_sanitizer.secrets import RedactorConfig, redact, redact_map
+
+redacted, found = redact("aws_key = AKIAIOSFODNN7EXAMPLE")
+# -> ("aws_key = [REDACTED: AWS Access Key]", ["AWS Access Key"])
+
+# Pass provider/host secret values in — config is supplied, never discovered.
+cfg = RedactorConfig(host_cred_vars={"GH_TOKEN": "ghp_realtokenvalue123"})
+redact("tok=ghp_realtokenvalue123", cfg)  # -> ("tok=[REDACTED: GH_TOKEN]", ["GH_TOKEN"])
+```
+
+### The rehydration map contract
+
+`redact_map(text, config)` returns a lossless, two-way view:
+
+```python
+{"text": "<redacted>",
+ "pairs": [{"placeholder": "[REDACTED: …]", "original": "<secret>", "start": <int>}],
+ "found": ["<type>", ...]}
+```
+
+Substituting each `pair["original"]` at its `start` reconstructs the input
+byte-for-byte. `start` is a **Unicode code-point** offset into `text` (the field
+is `start`, not `start_offset`). U+E000 / U+E001 are reserved placeholder
+sentinels: input already containing either is refused with
+`{"unmappable": "input contains reserved sentinel characters"}` (fail closed)
+rather than producing an ambiguous map.
+
+### Daemon vs. one-shot
+
+detect-secrets caches a process-global `secret_type → plugin` mapping, so a fresh
+one-shot call must re-register the plugin set every time — slow under load. Two
+console scripts (installed with the extra) cover both modes:
+
+- **`agent-secret-redactor`** — one-shot: reads text on stdin, writes the
+  redaction result as JSON on stdout. Re-registers plugins per call.
+- **`agent-secret-redactor-daemon <socket-path>`** — long-lived Unix-socket
+  server that configures the plugin set **once** at startup (a warm-up scan
+  primes the cache before it binds, so a bound socket means ready). Wire protocol
+  both directions: a 4-byte big-endian length prefix then that many bytes of
+  UTF-8 JSON. Request `{"text", "map", "web_ingress", "env_secrets"}`; response is
+  the one-shot result, JSON `null` when nothing is redacted, or `{"error": …}` on
+  a scan failure.
+
+Both console scripts import the engine on startup, so they fail loud if the
+`[secrets]` extra (hence `detect-secrets`) is not installed — fail closed, never
+a silent no-op.
+
+## Versioning
+
+This package is versioned in lockstep with the npm
+[`agent-sanitizer`](https://www.npmjs.com/package/agent-sanitizer):
+each release publishes both at the same version from the same commit, and the
+wheel bundles `src/` at exactly that version. So `pip install
+agent-sanitizer==X.Y.Z` and `npm i agent-sanitizer@X.Y.Z` are the
+same underlying logic.

agent_sanitizer-2.0.0/README.md

@@ -0,0 +1,115 @@
+# agent-sanitizer (Python client)
+
+A thin Python bridge to the [`agent-sanitizer`](https://github.com/AlexanderMattTurner/agent-sanitizer)
+Node.js CLI. The sanitization logic has a single source of truth — the
+JavaScript in `src/` — so this package shells out to the CLI rather than
+re-implementing it, giving a Python pipeline byte-identical verdicts with no
+second implementation to keep in sync.
+
+## Requirements
+
+- **Node.js (>= 22) on `PATH`.** The sanitizer is JavaScript; something has to
+  run it. There is deliberately no pure-Python fallback.
+
+That's it — `pip install agent-sanitizer` and, with Node available, you're
+ready to go. The wheel ships a self-contained, single-file build of the CLI
+(the `src/` logic and its npm dependencies bundled into one `.mjs` at release
+time), so there is no separate JavaScript checkout to clone and no environment
+variable to set. The bundle is a versioned build artifact from `src/`, not a
+hand-maintained port, so it can't drift from the JS.
+
+### Optional: point at your own JS checkout
+
+Set `AGENT_SANITIZER_CLI` to a checkout's `bin/sanitize-cli.mjs` to override the
+bundled CLI (e.g. to run against unreleased `src/` changes). When the module is
+imported directly from a repo checkout, the source CLI is found automatically.
+
+## Usage
+
+```python
+from agent_sanitizer import sanitize
+
+result = sanitize("untrusted text", html=True)
+print(result.cleaned, result.found, result.warnings)
+```
+
+See the package docstring for the full set of entry points (`sanitize_text`,
+`classify_prompt`, `scan_instruction_files`, `clean_file`, and the long-lived
+`Sanitizer` worker).
+
+## Secret redaction (`[secrets]` extra)
+
+The base install is dependency-free. The optional `secrets` extra adds a
+pure-Python secret-redaction engine under `agent_sanitizer.secrets` —
+detect-secrets plus custom detectors, benign-value skipping, cross-line
+reassembly, PEM collapse, and exact-match redaction of caller-supplied env-var
+values. Unlike the sanitizer above it needs **no Node.js**; its only dependency
+is `detect-secrets`, pulled in by the extra:
+
+```bash
+pip install "agent-sanitizer[secrets]"
+```
+
+Every detect-secrets import lives inside this subpackage, so a plain
+`import agent_sanitizer` never touches it. The engine shares the parent
+package's invisible-character SSOT (`agent_sanitizer.invisible`) rather
+than forking it — a fork would be a silent security regression.
+
+### In-process
+
+```python
+from agent_sanitizer.secrets import RedactorConfig, redact, redact_map
+
+redacted, found = redact("aws_key = AKIAIOSFODNN7EXAMPLE")
+# -> ("aws_key = [REDACTED: AWS Access Key]", ["AWS Access Key"])
+
+# Pass provider/host secret values in — config is supplied, never discovered.
+cfg = RedactorConfig(host_cred_vars={"GH_TOKEN": "ghp_realtokenvalue123"})
+redact("tok=ghp_realtokenvalue123", cfg)  # -> ("tok=[REDACTED: GH_TOKEN]", ["GH_TOKEN"])
+```
+
+### The rehydration map contract
+
+`redact_map(text, config)` returns a lossless, two-way view:
+
+```python
+{"text": "<redacted>",
+ "pairs": [{"placeholder": "[REDACTED: …]", "original": "<secret>", "start": <int>}],
+ "found": ["<type>", ...]}
+```
+
+Substituting each `pair["original"]` at its `start` reconstructs the input
+byte-for-byte. `start` is a **Unicode code-point** offset into `text` (the field
+is `start`, not `start_offset`). U+E000 / U+E001 are reserved placeholder
+sentinels: input already containing either is refused with
+`{"unmappable": "input contains reserved sentinel characters"}` (fail closed)
+rather than producing an ambiguous map.
+
+### Daemon vs. one-shot
+
+detect-secrets caches a process-global `secret_type → plugin` mapping, so a fresh
+one-shot call must re-register the plugin set every time — slow under load. Two
+console scripts (installed with the extra) cover both modes:
+
+- **`agent-secret-redactor`** — one-shot: reads text on stdin, writes the
+  redaction result as JSON on stdout. Re-registers plugins per call.
+- **`agent-secret-redactor-daemon <socket-path>`** — long-lived Unix-socket
+  server that configures the plugin set **once** at startup (a warm-up scan
+  primes the cache before it binds, so a bound socket means ready). Wire protocol
+  both directions: a 4-byte big-endian length prefix then that many bytes of
+  UTF-8 JSON. Request `{"text", "map", "web_ingress", "env_secrets"}`; response is
+  the one-shot result, JSON `null` when nothing is redacted, or `{"error": …}` on
+  a scan failure.
+
+Both console scripts import the engine on startup, so they fail loud if the
+`[secrets]` extra (hence `detect-secrets`) is not installed — fail closed, never
+a silent no-op.
+
+## Versioning
+
+This package is versioned in lockstep with the npm
+[`agent-sanitizer`](https://www.npmjs.com/package/agent-sanitizer):
+each release publishes both at the same version from the same commit, and the
+wheel bundles `src/` at exactly that version. So `pip install
+agent-sanitizer==X.Y.Z` and `npm i agent-sanitizer@X.Y.Z` are the
+same underlying logic.