sak-guard 0.2.0a1__tar.gz

sak_guard-0.2.0a1/LICENSE

@@ -0,0 +1,217 @@
+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.
+
+------------------------------------------------------------------------------
+
+Copyright 2026 Pantronux Research (Lead: Irfan Achmad Firmansyah)
+
+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.

sak_guard-0.2.0a1/MANIFEST.in

@@ -0,0 +1,6 @@
+include LICENSE README.md pyproject.toml
+recursive-include sak_guard *.py py.typed
+recursive-include tests *.py
+recursive-include docs *.md
+global-exclude *.py[cod]
+global-exclude __pycache__

sak_guard-0.2.0a1/PKG-INFO

@@ -0,0 +1,220 @@
+Metadata-Version: 2.4
+Name: sak-guard
+Version: 0.2.0a1
+Summary: Static pre-commit security guardrail for Solana Agent Kit and agent-client code. The static complement to a runtime transaction firewall.
+Author: Pantronux Research (Lead: Irfan Achmad Firmansyah)
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/Pantronux-Research/sak-guard
+Project-URL: Repository, https://github.com/Pantronux-Research/sak-guard.git
+Project-URL: Issues, https://github.com/Pantronux-Research/sak-guard/issues
+Project-URL: Changelog, https://github.com/Pantronux-Research/sak-guard/releases
+Project-URL: Security, https://github.com/Pantronux-Research/sak-guard/security/policy
+Keywords: solana,security,static-analysis,solana-agent-kit,linter,guardrail,pre-commit,ai-agents
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: llm
+Requires-Dist: openai>=1.0; extra == "llm"
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == "dev"
+Requires-Dist: build>=1.0; extra == "dev"
+Dynamic: license-file
+
+# sak-guard
+
+[![CI](https://github.com/Pantronux-Research/sak-guard/actions/workflows/ci.yml/badge.svg)](https://github.com/Pantronux-Research/sak-guard/actions/workflows/ci.yml)
+[![License: Apache-2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://github.com/Pantronux-Research/sak-guard/blob/main/LICENSE)
+[![Python](https://img.shields.io/badge/python-%3E%3D3.10-blue.svg)](https://github.com/Pantronux-Research/sak-guard/blob/main/pyproject.toml)
+[![PyPI](https://img.shields.io/badge/PyPI-not%20yet%20published-lightgrey.svg)](https://pypi.org/project/sak-guard/)
+[![Status: alpha](https://img.shields.io/badge/status-alpha-orange.svg)](#status)
+
+**Static pre-commit security guardrail for Solana agent code.**
+The static complement to a runtime transaction firewall.
+
+> **Status: 0.2.0a1 release candidate.** Five Solana rule families are implemented.
+> This is an alpha heuristic guardrail. Read the [detection envelope](docs/DETECTION_ENVELOPE.md)
+> before using a passing result as a release decision.
+
+---
+
+## Why this exists
+
+Solana's agent ecosystem is adding transaction capability faster than safety tooling.
+`solana-agent-kit` lets an agent construct and submit transactions, and the community is
+patching the gap ad hoc — most visibly
+[`sendaifun/solana-agent-kit#575`](https://github.com/sendaifun/solana-agent-kit/issues/575),
+which proposes `@prflght/sak-plugin`, a plugin that wraps the SAK execution flow to
+**intercept every transaction before it lands on-chain**.
+
+That is a **runtime** control. It sees a transaction at the moment it is built. It does not
+see, and cannot stop, the bad *code* that builds it — an agent-authored tool that sources a
+keypair from the wrong place, leaks a seed into a prompt, or does something other than what
+its description claims. By the time a runtime firewall has something to intercept, the
+vulnerable code is already merged and running.
+
+`sak-guard` asks a different question, earlier:
+
+> Before this code is merged — does it do what it claims to do, and does it handle keys and
+> transactions safely?
+
+The two are **complements, not competitors**. Use both.
+
+## Install
+
+```bash
+# Install this unpublished candidate from the reviewed checkout:
+python -m pip install .
+```
+
+Requires **Python >= 3.10** (see [why the floor is 3.10 rather than 3.9](https://github.com/Pantronux-Research/sak-guard/blob/main/pyproject.toml)).
+
+No runtime dependencies — the engine is stdlib-only, so a pre-commit hook does not have to
+touch your environment.
+
+## Use
+
+```bash
+sak-guard FILE|DIR            # audit a file or a tree
+sak-guard -                   # Python source on stdin (not a git diff)
+sak-guard F --json            # machine-readable
+sak-guard F --fail-on X       # critical | high | medium | low | any | never
+sak-guard F --strategy S      # security-focused (default) | default | ast-heavy | intent-focused
+sak-guard F --intent "..."    # what the code is supposed to do
+sak-guard F --use-llm         # optional LLM intent pass (provider from LLM_* env)
+sak-guard F --language python # source language (default: python)
+sak-guard F --quiet           # only print failing targets
+```
+
+Exit codes: **0** clean or below threshold · **1** findings at/above threshold · **2** usage,
+IO, parse or incomplete-analysis error. Scan errors remain exit 2 with `--fail-on never`.
+That option suppresses the failure status for completed findings only.
+
+`reports[].passed` means there are no High/Critical findings; it is independent of
+the selected CLI threshold. An incomplete report always has `passed: false`.
+
+```console
+$ sak-guard tests/fixtures/vulnerable_api.py
+tests/fixtures/vulnerable_api.py: 3 issue(s) (confidence 0.95)
+  [critical]:13 security: Hardcoded secret/credential detected
+      fix: Use environment variables or a secrets manager
+  [critical]:23 security: Use of eval() is a security risk — allows arbitrary code execution
+      fix: Use ast.literal_eval() for safe evaluation or avoid eval entirely
+  [high]:9 security: subprocess with shell=True allows shell injection
+      fix: Use shell=False and pass args as a list
+
+3 issue(s) across 1 target(s); fail-on=high
+$ echo $?
+1
+```
+
+### Why the default strategy is `security-focused`
+
+The base analyzer bank covers hardcoded secrets and `eval()`. It does **not** look for shell
+injection at all — no `os.system` or `shell=True` pattern exists in it. Those live in the
+`security-focused` strategy's extra patterns. A security auditor defaulting to the base bank
+reports **"clean" on `subprocess.call(cmd, shell=True)`**. So the CLI defaults to the bank
+that actually looks for command injection.
+
+Verify this yourself: run the same fixture with `--strategy default` and count.
+
+## Pre-commit
+
+```yaml
+# .pre-commit-config.yaml
+repos:
+  - repo: https://github.com/Pantronux-Research/sak-guard
+    rev: v0.2.0-alpha.1 # use the reviewed release tag once it exists
+    hooks:
+      - id: sak-guard
+        args: ["--fail-on", "high"]
+```
+
+Each pre-commit file scan uses its own isolated process. Budget roughly 0.1
+seconds of process startup per small file on the review machine; 100 files can
+add about 10 seconds before substantial analysis. Measure this on your runner.
+For larger projects, scope the consumer hook to all key-handling and
+transaction-building paths, for example:
+
+```yaml
+      - id: sak-guard
+        files: ^(src/transaction_client/|src/agents/|tests/solana/)
+        require_serial: true
+        args: ["--fail-on", "high"]
+```
+
+Replace those example paths with your own complete set. Files outside the filter
+receive no checks. `require_serial` avoids competing hook processes on a loaded
+runner; it does not reuse workers. The 15-second deadline is a per-file analysis
+budget, not a promise that every valid generated module fits it. A timeout exits
+2 and requires investigation; it never becomes a passing verdict.
+
+## GitHub Actions
+
+```yaml
+- run: python -m pip install .
+- run: sak-guard src/ --fail-on high
+```
+
+## Three engines
+
+1. **AST analysis** — structural inspection: where keypairs are sourced, whether transaction
+   construction is validated, whether signing is gated.
+2. **Security pattern banks** — AST checks for hardcoded secrets, `eval`/`exec`,
+   `subprocess(..., shell=True)` and unsafe deserialization. Text heuristics supply
+   additional advisory diagnostics.
+3. **Intent-mismatch verification** *(in progress)* — declare what a tool is *supposed* to
+   do; fail the build when the implementation diverges. No existing Solana safety tool does
+   this statically.
+
+## Detection envelope
+
+**Read this before treating a pass as proof.** `sak-guard` is static analysis. It will miss
+whole vulnerability classes:
+
+- anything depending on **runtime state**, **economic conditions**, or **on-chain state** —
+  none of which exist at commit time;
+- logic errors that are syntactically safe;
+- vulnerabilities in dependencies.
+
+It is not a replacement for a runtime firewall, a fuzzer, or a formal audit. We publish our
+detection gaps and false-positive rate rather than hide them, because a safety tool that
+overstates its coverage **is itself a risk**. Current measured rates are in
+[`VERIFICATION.md`](VERIFICATION.md).
+
+The [current rule contract](docs/DETECTION_ENVELOPE.md) describes the signing and amount
+proxies, conservative false positives, resource limits and unsupported flows. Historical
+verification reports describe their own snapshots, not this release candidate.
+
+Each CLI file scan has a 15-second worker deadline (60 seconds with explicit LLM use),
+a 4 MiB source limit and a 200,000-node AST limit. Analysis never imports or executes
+submitted code. Only `--use-llm` permits sending source to a configured provider.
+
+## Roadmap
+
+- [x] Decoupled CLI, stdlib-only, no server
+- [x] AST + regex engines with verified pass/fail behaviour
+- [x] Initial Solana banks: key handling, RPC, model provenance, signing and amount bounds
+- [ ] GitHub Action with inline PR annotations
+- [ ] Intent-mismatch verification, published fixtures
+- [x] Documented detection envelope and regression fixtures
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).
+
+---
+
+*Pantronux Research (Lead: Irfan Achmad Firmansyah) — Indonesia*

sak_guard-0.2.0a1/README.md

@@ -0,0 +1,185 @@
+# sak-guard
+
+[![CI](https://github.com/Pantronux-Research/sak-guard/actions/workflows/ci.yml/badge.svg)](https://github.com/Pantronux-Research/sak-guard/actions/workflows/ci.yml)
+[![License: Apache-2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://github.com/Pantronux-Research/sak-guard/blob/main/LICENSE)
+[![Python](https://img.shields.io/badge/python-%3E%3D3.10-blue.svg)](https://github.com/Pantronux-Research/sak-guard/blob/main/pyproject.toml)
+[![PyPI](https://img.shields.io/badge/PyPI-not%20yet%20published-lightgrey.svg)](https://pypi.org/project/sak-guard/)
+[![Status: alpha](https://img.shields.io/badge/status-alpha-orange.svg)](#status)
+
+**Static pre-commit security guardrail for Solana agent code.**
+The static complement to a runtime transaction firewall.
+
+> **Status: 0.2.0a1 release candidate.** Five Solana rule families are implemented.
+> This is an alpha heuristic guardrail. Read the [detection envelope](docs/DETECTION_ENVELOPE.md)
+> before using a passing result as a release decision.
+
+---
+
+## Why this exists
+
+Solana's agent ecosystem is adding transaction capability faster than safety tooling.
+`solana-agent-kit` lets an agent construct and submit transactions, and the community is
+patching the gap ad hoc — most visibly
+[`sendaifun/solana-agent-kit#575`](https://github.com/sendaifun/solana-agent-kit/issues/575),
+which proposes `@prflght/sak-plugin`, a plugin that wraps the SAK execution flow to
+**intercept every transaction before it lands on-chain**.
+
+That is a **runtime** control. It sees a transaction at the moment it is built. It does not
+see, and cannot stop, the bad *code* that builds it — an agent-authored tool that sources a
+keypair from the wrong place, leaks a seed into a prompt, or does something other than what
+its description claims. By the time a runtime firewall has something to intercept, the
+vulnerable code is already merged and running.
+
+`sak-guard` asks a different question, earlier:
+
+> Before this code is merged — does it do what it claims to do, and does it handle keys and
+> transactions safely?
+
+The two are **complements, not competitors**. Use both.
+
+## Install
+
+```bash
+# Install this unpublished candidate from the reviewed checkout:
+python -m pip install .
+```
+
+Requires **Python >= 3.10** (see [why the floor is 3.10 rather than 3.9](https://github.com/Pantronux-Research/sak-guard/blob/main/pyproject.toml)).
+
+No runtime dependencies — the engine is stdlib-only, so a pre-commit hook does not have to
+touch your environment.
+
+## Use
+
+```bash
+sak-guard FILE|DIR            # audit a file or a tree
+sak-guard -                   # Python source on stdin (not a git diff)
+sak-guard F --json            # machine-readable
+sak-guard F --fail-on X       # critical | high | medium | low | any | never
+sak-guard F --strategy S      # security-focused (default) | default | ast-heavy | intent-focused
+sak-guard F --intent "..."    # what the code is supposed to do
+sak-guard F --use-llm         # optional LLM intent pass (provider from LLM_* env)
+sak-guard F --language python # source language (default: python)
+sak-guard F --quiet           # only print failing targets
+```
+
+Exit codes: **0** clean or below threshold · **1** findings at/above threshold · **2** usage,
+IO, parse or incomplete-analysis error. Scan errors remain exit 2 with `--fail-on never`.
+That option suppresses the failure status for completed findings only.
+
+`reports[].passed` means there are no High/Critical findings; it is independent of
+the selected CLI threshold. An incomplete report always has `passed: false`.
+
+```console
+$ sak-guard tests/fixtures/vulnerable_api.py
+tests/fixtures/vulnerable_api.py: 3 issue(s) (confidence 0.95)
+  [critical]:13 security: Hardcoded secret/credential detected
+      fix: Use environment variables or a secrets manager
+  [critical]:23 security: Use of eval() is a security risk — allows arbitrary code execution
+      fix: Use ast.literal_eval() for safe evaluation or avoid eval entirely
+  [high]:9 security: subprocess with shell=True allows shell injection
+      fix: Use shell=False and pass args as a list
+
+3 issue(s) across 1 target(s); fail-on=high
+$ echo $?
+1
+```
+
+### Why the default strategy is `security-focused`
+
+The base analyzer bank covers hardcoded secrets and `eval()`. It does **not** look for shell
+injection at all — no `os.system` or `shell=True` pattern exists in it. Those live in the
+`security-focused` strategy's extra patterns. A security auditor defaulting to the base bank
+reports **"clean" on `subprocess.call(cmd, shell=True)`**. So the CLI defaults to the bank
+that actually looks for command injection.
+
+Verify this yourself: run the same fixture with `--strategy default` and count.
+
+## Pre-commit
+
+```yaml
+# .pre-commit-config.yaml
+repos:
+  - repo: https://github.com/Pantronux-Research/sak-guard
+    rev: v0.2.0-alpha.1 # use the reviewed release tag once it exists
+    hooks:
+      - id: sak-guard
+        args: ["--fail-on", "high"]
+```
+
+Each pre-commit file scan uses its own isolated process. Budget roughly 0.1
+seconds of process startup per small file on the review machine; 100 files can
+add about 10 seconds before substantial analysis. Measure this on your runner.
+For larger projects, scope the consumer hook to all key-handling and
+transaction-building paths, for example:
+
+```yaml
+      - id: sak-guard
+        files: ^(src/transaction_client/|src/agents/|tests/solana/)
+        require_serial: true
+        args: ["--fail-on", "high"]
+```
+
+Replace those example paths with your own complete set. Files outside the filter
+receive no checks. `require_serial` avoids competing hook processes on a loaded
+runner; it does not reuse workers. The 15-second deadline is a per-file analysis
+budget, not a promise that every valid generated module fits it. A timeout exits
+2 and requires investigation; it never becomes a passing verdict.
+
+## GitHub Actions
+
+```yaml
+- run: python -m pip install .
+- run: sak-guard src/ --fail-on high
+```
+
+## Three engines
+
+1. **AST analysis** — structural inspection: where keypairs are sourced, whether transaction
+   construction is validated, whether signing is gated.
+2. **Security pattern banks** — AST checks for hardcoded secrets, `eval`/`exec`,
+   `subprocess(..., shell=True)` and unsafe deserialization. Text heuristics supply
+   additional advisory diagnostics.
+3. **Intent-mismatch verification** *(in progress)* — declare what a tool is *supposed* to
+   do; fail the build when the implementation diverges. No existing Solana safety tool does
+   this statically.
+
+## Detection envelope
+
+**Read this before treating a pass as proof.** `sak-guard` is static analysis. It will miss
+whole vulnerability classes:
+
+- anything depending on **runtime state**, **economic conditions**, or **on-chain state** —
+  none of which exist at commit time;
+- logic errors that are syntactically safe;
+- vulnerabilities in dependencies.
+
+It is not a replacement for a runtime firewall, a fuzzer, or a formal audit. We publish our
+detection gaps and false-positive rate rather than hide them, because a safety tool that
+overstates its coverage **is itself a risk**. Current measured rates are in
+[`VERIFICATION.md`](VERIFICATION.md).
+
+The [current rule contract](docs/DETECTION_ENVELOPE.md) describes the signing and amount
+proxies, conservative false positives, resource limits and unsupported flows. Historical
+verification reports describe their own snapshots, not this release candidate.
+
+Each CLI file scan has a 15-second worker deadline (60 seconds with explicit LLM use),
+a 4 MiB source limit and a 200,000-node AST limit. Analysis never imports or executes
+submitted code. Only `--use-llm` permits sending source to a configured provider.
+
+## Roadmap
+
+- [x] Decoupled CLI, stdlib-only, no server
+- [x] AST + regex engines with verified pass/fail behaviour
+- [x] Initial Solana banks: key handling, RPC, model provenance, signing and amount bounds
+- [ ] GitHub Action with inline PR annotations
+- [ ] Intent-mismatch verification, published fixtures
+- [x] Documented detection envelope and regression fixtures
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).
+
+---
+
+*Pantronux Research (Lead: Irfan Achmad Firmansyah) — Indonesia*