granttrace 2.4.0__tar.gz

granttrace-2.4.0/CHANGELOG.md

@@ -0,0 +1,151 @@
+# Changelog
+
+## 2.4.0 - 2026-10-03
+
+### Added
+
+- Generate offline OpenAPI configuration drafts and missing-input checklists;
+  reject unresolved drafts and refuse to overwrite existing files.
+- Add offline HTML report search/status filters and compact severity labels.
+- Support strict OpenAPI style/explode and Swagger collectionFormat parameter
+  serialization in scans/readbacks, including arrays and lowercase booleans;
+  decline unsupported or ambiguous formats before sending requests.
+- Add explicit per-pair expected_visitor_access for legitimate sharing/admin
+  reads, recorded as AUTHORIZED, and six local authorization truth fixtures with
+  false-positive/false-negative accounting.
+- Add mandatory Ruff checks, real unittest branch coverage with text/XML/JSON
+  evidence, runtime dependency auditing with pip-audit, and a Python CodeQL
+  workflow. Keep mypy advisory while recording existing type debt.
+- Add simple issue templates and contribution guidance with private vulnerability
+  reporting and reminders to exclude credentials and sensitive target data.
+
+### Changed
+
+- Promote the previously identified 2.4.0.dev0 development build to 2.4.0 across
+  runtime, package metadata and reports; retain api_sentinel.py and
+  APISentinelAuditor compatibility.
+- Use granttrace_report.html when no output path is supplied and align package
+  description, version status and GrantTrace branding.
+- Keep a concise five-minute README walkthrough, add identity/readback/restoration
+  highlights, and preserve the visible report preview and detailed guide links.
+- Explain identity/resource access, changed fields, restoration and next steps
+  before raw evidence. JSON report schema is version 2.
+- Remove tests' dependence on untracked config.json; automate JSON/YAML mock
+  restoration and clean wheel installation outside the checkout in CI.
+- Maintain reproducible release verification and local-output ignore rules;
+  remove an unused demo image while preserving the report preview.
+- Include example configuration, guides and verification scripts in the source
+  distribution so its documented local checks can be reproduced.
+
+### Security / Safety
+
+- Preserve default read-only auditing and explicit allowlisted JSON PATCH checks;
+  active POST/PUT checks and automated authentication are not added.
+- Preserve independent GET readback, original-state snapshots, finally-protected
+  restoration and rollback verification. Failed recovery halts subsequent writes.
+- Preserve TLS verification by default, explicit non-loopback HTTP opt-in and
+  minimized/redacted evidence by default.
+- Retain denial, anonymous-leak and invalid-baseline boundaries without changing
+  the BOLA / IDOR or Mass Assignment detection criteria during release preparation.
+
+Historical release tags and assets, including v2.3.1, remain unchanged.
+
+## 2.3.1 - Verified authorization, snapshot and credential fixes
+
+- Require trustworthy, clean anonymous rejection before a visitor-denial branch
+  can produce endpoint-level SECURE; leaked business data remains suspicious.
+- Reject non-standard JSON constants and overflowing floats in response parsing.
+  Validate the original snapshot and finite request payloads before any PATCH;
+  preserve recovery when a post-write readback is invalid.
+- Redact component values from request Cookie headers, including names such as
+  path/domain/secure/version, quoted/encoded echoes and known numeric credentials.
+- Align readback parameter arrays, elements and override mappings between the
+  editor schema, semantic validator and runtime.
+- Load the same JSON/YAML specification authentication context in configuration
+  validation and scanning; reject explicit invalid specifications cleanly.
+- Validate the effective CLI write allowlist against its own readback mappings.
+- Add 45 regression tests across four release modules; all 223 tests pass with
+  real PyYAML installed. Repeat complete CLI mock audits for JSON and YAML and
+  confirm full database restoration.
+- Build/install the 2.3.1 wheel and smoke-test its installed console entry point;
+  refresh sample reports and record current verification separately from history.
+
+## 2.3.0 (v2.3.0-final) - Configuration validation, authoritative identity rules, and release hardening
+
+- **Authoritative Configuration Validator (`core/config_validator.py`)**:
+  - Implemented offline semantic validation engine for `config.json` without external network requests.
+  - Added `--validate-config` CLI flag for pre-flight validation (exit code 0 for valid, 2 for invalid), without target-network requests or state-changing target actions.
+  - Normal CLI scanning automatically runs the authoritative preflight check, rejecting invalid configurations before creating the auditor or sending any HTTP requests.
+  - Enforced single canonical format for operation keys (`<METHOD> /<path>` with strictly single space), consistent case handling, and spelling error suggestions (Levenshtein distance).
+  - Implemented symmetric two-way path collision detection (`paths_collide`) between `ignore_readback_paths` and written/readback paths across both validator and transaction rollback.
+  - Unified authentication header recognition rules between Validator and Auditor, standardizing `session`, `credential`, custom `auth_header_names`, and OpenAPI-declared security schemes.
+
+- **Schema and Exemplary Assets**:
+  - Added standard `config.schema.json` (JSON Schema Draft-07) for editor autocomplete, hover documentation, and structural validation.
+  - Added comprehensive `config.example.json` with `$schema` linkage, sample identities, readbacks, and BOLA policies.
+
+- **Security and Robustness Hardening**:
+  - Bound recursion depth (`MAX_RECURSION_DEPTH = 15`) and explicitly reject non-standard JSON numeric values (`NaN`, `Infinity`).
+  - Strict credential sanitization across all diagnostic outputs (`Actual`, `Expected`, errors) and stripped CR/LF/control characters to mitigate known log-injection paths.
+
+- **Core Detection Behavior Compatibility**:
+  - No intentional behavior changes were made to BOLA decisions, snapshot recovery, diff, generator, or parser logic in this release; all existing regression tests continue to pass.
+
+- **Test Suite Expansion**:
+  - Total automated tests expanded from 118 to 178 (all 178 passing, 0 failures, 0 errors).
+  - Added 22 offline configuration validation tests (`tests/test_config_validation.py`).
+  - Added 20 security and sanitization tests (`tests/test_rc2_security_hardening.py`).
+  - Added 18 strict regression counterexample tests (`tests/test_rc3_hardening.py`).
+
+- **Packaging Hygiene and Metadata**:
+  - Standardized Python package version in `pyproject.toml` to PEP 440 compliant `2.3.0`, with GitHub / ZIP delivery tag designated as `v2.3.0-final`.
+  - Purged all build artifacts, temporary test reports (`API_Security_Report.html`, `result.json`), and caches (`__pycache__`, `*.pyc`, `.pytest_cache`, `.git`) from the distribution archive.
+
+## 2.2.0 - Regression-driven safety fixes
+
+- Snapshot/recover complete written fields, objects and arrays using original
+  business values; compare the full readback state, including derived changes.
+- Recover after mutation/readback exceptions, guard recovery's own exceptions,
+  and stop later writes on failed verification or asynchronous acceptance.
+- Require configured strong readback consistency for unchanged-write SECURE.
+- Do not mistake 403-with-data, historical denial text, anonymous private
+  increments, or undeclared public access for access-control enforcement.
+- Compare effective authentication headers; exclude request/trace echoes from
+  identity evidence and support explicit trusted response resource_id_paths.
+- Probe readOnly privilege fields while excluding them from ordinary baselines.
+- Recursively validate samples, intersect allOf constraints and reject invalid
+  baselines. Resolve 3.1 ref siblings in their original contexts; reject ambiguous
+  3.0/Swagger structural siblings and missing pointers instead of losing fields.
+- Propagate supported media types, rejecting unsupported JSON Patch arrays.
+- Bound/redact bodies, URLs, known credentials, error text and result metadata.
+- Add zero-check CI failure, coverage/suspicious gates, no-network dry-run and
+  case-sensitive CLI allowlist replacement.
+
+Migration: PUBLIC needs explicit policy; unchanged active checks need strong
+readback consistency. Rewrite 3.0 structural ref siblings as allOf. Full-state
+verification may require explicitly identifying harmless volatile fields. These
+checks do not establish a universal rollback or privacy guarantee.
+
+## 2.1.0 - Safety hardening
+
+- Made read-only auditing the default and limited active mutations to explicitly
+  allowlisted JSON `PATCH` operations.
+- Added independent read-before/write/read-after/rollback verification, retrying
+  readback and treating asynchronous or ambiguous outcomes as errors.
+- Reworked BOLA decisions around owner, cross-visitor, anonymous, and distinct
+  visitor-self baselines. Matching JSON structure alone is never confirmation.
+- Added explicit `CONFIRMED`, `SECURE`, `PUBLIC`, `SUSPICIOUS`, `INCONCLUSIVE`,
+  `SKIPPED`, and `ERROR` results with honest attempted/conclusive coverage.
+- Enabled TLS verification by default, blocked redirects, capped response sizes,
+  added global throttling, and restricted non-loopback clear-text HTTP.
+- Added default evidence minimisation, secret/PII redaction, hashes, and HTML
+  escaping.
+- Expanded OpenAPI parsing to JSON/YAML, safe local external references,
+  recursive schemas/compositions, and parameter override semantics.
+- Added constraint-aware parameters, valid request baselines, and one-field
+  nested mass-assignment mutations.
+- Added packaging metadata, CI, an Apache-2.0 license, security guidance, and a
+  standard-library regression suite.
+
+The bundled mock remains intentionally vulnerable in one BOLA route and one
+mass-assignment route so the end-to-end flow can be verified safely on loopback.

granttrace-2.4.0/CONTRIBUTING.md

@@ -0,0 +1,47 @@
+# Contributing to GrantTrace
+
+Use Python 3.9 or newer. Create a branch from the latest `main`, then install
+the development dependencies:
+
+```bash
+git switch -c your-change
+python -m pip install -e ".[dev]" "setuptools>=77" wheel
+```
+
+Run the regression suite, local verification scripts and Ruff before opening a PR:
+
+```bash
+python -m unittest discover -s tests
+python scripts/verify_business_scenarios.py
+python scripts/verify_examples.py
+python scripts/verify_install.py
+python -m ruff check .
+```
+
+Measure coverage with the actual regression suite:
+
+```bash
+python -m coverage erase
+python -m coverage run -m unittest discover -s tests
+python -m coverage report
+python -m coverage xml
+python -m coverage json
+```
+
+Mypy is advisory while existing dynamic JSON type issues are tracked:
+
+```bash
+python -m mypy
+```
+
+Keep PRs focused. Explain the problem, the resulting behavior and the checks you
+actually ran. Preserve detection semantics and the write allowlist, independent
+readback and recovery safeguards. Add useful regression cases for changed
+behavior; do not add tests solely to raise the coverage percentage. Use only the
+bundled loopback mock or isolated systems you are explicitly authorized to test.
+
+Never commit real tokens, cookies, API keys, account credentials, production data,
+or sensitive identity information. Redact examples and reports before sharing.
+Report vulnerabilities through GitHub's
+[Private Vulnerability Reporting](https://github.com/ysc070528/granttrace/security/advisories/new),
+following [SECURITY.md](SECURITY.md), rather than a public issue.

granttrace-2.4.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 [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.

granttrace-2.4.0/MANIFEST.in

@@ -0,0 +1,8 @@
+include CHANGELOG.md CONTRIBUTING.md SECURITY.md VERIFICATION.md
+include config.example.json config.schema.json openapi.json test_suite.py
+recursive-include scripts *.py
+recursive-include tests *.py
+recursive-include docs *.md
+include docs/assets/report-preview.png
+include examples/README.md examples/sample_report.html examples/sample_result.json
+global-exclude __pycache__ *.py[cod] *.local.json

granttrace-2.4.0/PKG-INFO

@@ -0,0 +1,108 @@
+Metadata-Version: 2.4
+Name: granttrace
+Version: 2.4.0
+Summary: Safety-first OpenAPI authorization auditing tool for BOLA, IDOR and Mass Assignment testing
+Author: GrantTrace contributors
+License-Expression: Apache-2.0
+Project-URL: Repository, https://github.com/ysc070528/granttrace
+Project-URL: Issues, https://github.com/ysc070528/granttrace/issues
+Project-URL: Changelog, https://github.com/ysc070528/granttrace/blob/main/CHANGELOG.md
+Classifier: Development Status :: 4 - Beta
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Security
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: PyYAML>=6.0
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: ruff<1,>=0.6; extra == "dev"
+Requires-Dist: mypy<3,>=1.11; extra == "dev"
+Requires-Dist: coverage[toml]<8,>=7.6; extra == "dev"
+Requires-Dist: types-PyYAML<7,>=6; extra == "dev"
+Dynamic: license-file
+
+# GrantTrace
+
+![CI](https://github.com/ysc070528/granttrace/actions/workflows/test.yml/badge.svg)
+![Python](https://img.shields.io/badge/python-3.9%2B-blue)
+![License](https://img.shields.io/badge/license-Apache--2.0-green)
+
+**Stable:** [v2.4.0](https://github.com/ysc070528/granttrace/releases/tag/v2.4.0)
+
+An OpenAPI authorization auditor that compares identities, verifies persisted changes, and reports restoration evidence.
+
+安全优先、证据驱动的 OpenAPI 权限审计工具。检查 BOLA / IDOR 与 Mass Assignment，输出身份对比、持久化变更及恢复核验的 HTML / JSON 报告。默认只读；主动写测试须显式开启并配置允许清单与独立读回。
+
+[五分钟体验](#五分钟体验) · [完整示例报告](examples/sample_report.html) · [配置指南](docs/configuration.md) · [命令行与迁移](docs/advanced.md) · [验收记录](VERIFICATION.md) · [发布自检](docs/release-checklist.md)
+
+## 为什么是 GrantTrace / Why GrantTrace
+
+- **Compare identities**：比较 Owner / Visitor / Anonymous 等身份访问同一资源的结果。
+- **Verify real side effects**：通过独立读回验证状态是否真正持久化，不只看 HTTP 状态码。
+- **Restore safely**：主动 PATCH 测试使用显式 allowlist、原始状态快照、恢复与恢复验证。
+
+<img src="docs/assets/report-preview.png" alt="GrantTrace 报告：身份访问摘要、修复建议和端点筛选" width="900">
+
+## 五分钟体验
+
+需要 Python 3.9+。在终端中克隆、安装并启动本机演示服务：
+
+```bash
+git clone https://github.com/ysc070528/granttrace.git
+cd granttrace
+python -m pip install -e .
+python mock_server/server.py
+```
+
+另开终端，进入同一目录执行首次只读扫描：
+
+```bash
+granttrace --spec openapi.json --target http://127.0.0.1:8080 --config config.example.json --export-json result.local.json
+```
+
+用浏览器打开默认生成的 **`granttrace_report.html`**：先查看发现与修复建议，再按状态筛选端点、展开证据。预期结果为 **1 个 CONFIRMED、1 个 PUBLIC、1 个 SECURE、2 个 SKIPPED**，确定性覆盖率 **60%**。两个 PATCH 因默认只读而跳过。JSON 结果写入 `result.local.json`；两个本地产物均由 `.gitignore` 忽略。
+
+在这个可丢弃的本地靶场体验写测试和恢复核验：
+
+```bash
+granttrace --spec openapi.json --target http://127.0.0.1:8080 --config config.example.json --allow-write-tests --export-json result.local.json
+```
+
+再次打开 **`granttrace_report.html`**。预期 **2 个 CONFIRMED、1 个 PUBLIC、2 个 SECURE**，确定性覆盖率 **100%**，批量赋值发现的 `rollback_verified` 为 `true`。本次扫描更新同名 HTML / JSON 文件；这些结果只属于内置五个演示端点。
+
+完整离线示例：[HTML 报告](examples/sample_report.html)（下载后用浏览器打开）与 [JSON 结果](examples/sample_result.json)。
+
+## 接入自己的 API
+
+先从规范生成配置草稿和待填清单：
+
+```bash
+granttrace --spec your-openapi.yaml --init-config config.local.json
+```
+
+填写不同的测试账户、各自资源、授权预期和必要读回信息，再按清单移除草稿标记与全部占位值。草稿未完成时会阻止预检、计划与扫描；写允许清单默认为空。
+
+```bash
+granttrace --spec your-openapi.yaml --config config.local.json --validate-config
+granttrace --spec your-openapi.yaml --config config.local.json --dry-run --export-json plan.local.json
+```
+
+账户、API Key / Cookie、合法共享和管理员访问配置见 [配置指南](docs/configuration.md)。支持的数组、布尔值及 `style` / `explode` 编码见 [参数规则](docs/parameter-serialization.md)。接入实测前请核对 [安全边界](SECURITY.md)。
+
+## 验证与边界
+
+```bash
+python -m unittest discover -s tests
+python scripts/verify_business_scenarios.py
+python scripts/verify_install.py
+```
+
+测试直接使用仓库中的 `config.example.json`，无需创建本地凭据文件。[业务场景验收](docs/business-scenarios.md) 单独记录团队共享、管理员读取、跨租户拒绝和故意越权的真值、误报与漏报；[验收记录](VERIFICATION.md) 标明实际测试环境和范围。
+
+“没有确认漏洞”不等于系统安全。检查覆盖率、错误、可疑和不确定项；显式授权预期只适用于本次身份与资源组合。仅在具备专用测试账户、独立读回和恢复方案的隔离环境启用写测试。远程 `$ref`、GraphQL、gRPC、自动 OAuth / mTLS 登录以及 POST / PUT 主动测试尚未实现。更多规则与迁移说明见 [操作指南](docs/advanced.md)。
+
+Apache License 2.0。

granttrace-2.4.0/README.md

@@ -0,0 +1,81 @@
+# GrantTrace
+
+![CI](https://github.com/ysc070528/granttrace/actions/workflows/test.yml/badge.svg)
+![Python](https://img.shields.io/badge/python-3.9%2B-blue)
+![License](https://img.shields.io/badge/license-Apache--2.0-green)
+
+**Stable:** [v2.4.0](https://github.com/ysc070528/granttrace/releases/tag/v2.4.0)
+
+An OpenAPI authorization auditor that compares identities, verifies persisted changes, and reports restoration evidence.
+
+安全优先、证据驱动的 OpenAPI 权限审计工具。检查 BOLA / IDOR 与 Mass Assignment，输出身份对比、持久化变更及恢复核验的 HTML / JSON 报告。默认只读；主动写测试须显式开启并配置允许清单与独立读回。
+
+[五分钟体验](#五分钟体验) · [完整示例报告](examples/sample_report.html) · [配置指南](docs/configuration.md) · [命令行与迁移](docs/advanced.md) · [验收记录](VERIFICATION.md) · [发布自检](docs/release-checklist.md)
+
+## 为什么是 GrantTrace / Why GrantTrace
+
+- **Compare identities**：比较 Owner / Visitor / Anonymous 等身份访问同一资源的结果。
+- **Verify real side effects**：通过独立读回验证状态是否真正持久化，不只看 HTTP 状态码。
+- **Restore safely**：主动 PATCH 测试使用显式 allowlist、原始状态快照、恢复与恢复验证。
+
+<img src="docs/assets/report-preview.png" alt="GrantTrace 报告：身份访问摘要、修复建议和端点筛选" width="900">
+
+## 五分钟体验
+
+需要 Python 3.9+。在终端中克隆、安装并启动本机演示服务：
+
+```bash
+git clone https://github.com/ysc070528/granttrace.git
+cd granttrace
+python -m pip install -e .
+python mock_server/server.py
+```
+
+另开终端，进入同一目录执行首次只读扫描：
+
+```bash
+granttrace --spec openapi.json --target http://127.0.0.1:8080 --config config.example.json --export-json result.local.json
+```
+
+用浏览器打开默认生成的 **`granttrace_report.html`**：先查看发现与修复建议，再按状态筛选端点、展开证据。预期结果为 **1 个 CONFIRMED、1 个 PUBLIC、1 个 SECURE、2 个 SKIPPED**，确定性覆盖率 **60%**。两个 PATCH 因默认只读而跳过。JSON 结果写入 `result.local.json`；两个本地产物均由 `.gitignore` 忽略。
+
+在这个可丢弃的本地靶场体验写测试和恢复核验：
+
+```bash
+granttrace --spec openapi.json --target http://127.0.0.1:8080 --config config.example.json --allow-write-tests --export-json result.local.json
+```
+
+再次打开 **`granttrace_report.html`**。预期 **2 个 CONFIRMED、1 个 PUBLIC、2 个 SECURE**，确定性覆盖率 **100%**，批量赋值发现的 `rollback_verified` 为 `true`。本次扫描更新同名 HTML / JSON 文件；这些结果只属于内置五个演示端点。
+
+完整离线示例：[HTML 报告](examples/sample_report.html)（下载后用浏览器打开）与 [JSON 结果](examples/sample_result.json)。
+
+## 接入自己的 API
+
+先从规范生成配置草稿和待填清单：
+
+```bash
+granttrace --spec your-openapi.yaml --init-config config.local.json
+```
+
+填写不同的测试账户、各自资源、授权预期和必要读回信息，再按清单移除草稿标记与全部占位值。草稿未完成时会阻止预检、计划与扫描；写允许清单默认为空。
+
+```bash
+granttrace --spec your-openapi.yaml --config config.local.json --validate-config
+granttrace --spec your-openapi.yaml --config config.local.json --dry-run --export-json plan.local.json
+```
+
+账户、API Key / Cookie、合法共享和管理员访问配置见 [配置指南](docs/configuration.md)。支持的数组、布尔值及 `style` / `explode` 编码见 [参数规则](docs/parameter-serialization.md)。接入实测前请核对 [安全边界](SECURITY.md)。
+
+## 验证与边界
+
+```bash
+python -m unittest discover -s tests
+python scripts/verify_business_scenarios.py
+python scripts/verify_install.py
+```
+
+测试直接使用仓库中的 `config.example.json`，无需创建本地凭据文件。[业务场景验收](docs/business-scenarios.md) 单独记录团队共享、管理员读取、跨租户拒绝和故意越权的真值、误报与漏报；[验收记录](VERIFICATION.md) 标明实际测试环境和范围。
+
+“没有确认漏洞”不等于系统安全。检查覆盖率、错误、可疑和不确定项；显式授权预期只适用于本次身份与资源组合。仅在具备专用测试账户、独立读回和恢复方案的隔离环境启用写测试。远程 `$ref`、GraphQL、gRPC、自动 OAuth / mTLS 登录以及 POST / PUT 主动测试尚未实现。更多规则与迁移说明见 [操作指南](docs/advanced.md)。
+
+Apache License 2.0。

granttrace-2.4.0/SECURITY.md

@@ -0,0 +1,59 @@
+# Security and safe operation
+
+GrantTrace sends requests to the target named on the command line. Use it
+only against systems for which you have explicit authorization.
+
+The default mode does not execute mutation checks. `--allow-write-tests`
+enables state-changing PATCH requests and must be limited to disposable test
+data. Every operation must be present in an explicit write allowlist. POST and
+PUT are not mutated automatically because generic compensation and full-state
+restoration cannot be inferred safely. Active checks require a JSON request
+schema plus a configured GET readback endpoint and explicit field mapping. When a
+change is observed, the scanner attempts to restore the original value and
+verifies the restoration. A rollback failure is reported as an error and must
+be investigated immediately.
+
+Since version 2.2, GrantTrace snapshots complete written containers and arrays, using observed
+business values instead of generated examples. Every possibly committed mutation
+passes through finally-protected recovery, including decode/readback exceptions.
+Recovery errors or HTTP 202 halt subsequent writes. Verification compares the
+entire readback document, not only payload fields. Explicit ignore_readback_paths
+may exclude known harmless volatile fields, but cannot overlap written snapshots.
+Never ignore privilege/derived-permission fields to make verification pass.
+
+This is not a database transaction. Forced termination, concurrent changes,
+late asynchronous work, logs, notifications and state not exposed by readback
+cannot be undone generically. Use disposable, isolated test resources. Only
+declare consistency=strong after checking the actual server/cache behavior;
+unchanged eventual or unspecified readback cannot establish SECURE. Restoration
+verification describes observed state, not a guarantee about all future state.
+
+Only object application/json and application/merge-patch+json are implemented.
+JSON Patch arrays, arbitrary vendor JSON and non-restorable Merge Patch null
+object members are not sent. Explicit CLI write selections replace the config
+allowlist; paths are case sensitive. Use --dry-run to inspect local scope without
+target requests. In CI, use --fail-on-error and an appropriate --min-coverage;
+--fail-on-suspicious also gates unresolved findings. Zero-check scans are not
+security passes.
+
+TLS certificate verification is enabled by default. Use `--insecure` only for
+an isolated test environment. Plain HTTP is accepted automatically only for
+loopback targets; other HTTP targets require `--allow-http`.
+
+Reports contain minimized and redacted evidence by default. The
+`--include-sensitive-evidence` option should be used only when the report will
+be stored with access controls appropriate for the target data.
+
+Non-JSON/broken bodies are omitted by default and represented by hashes. URL
+query values, known credentials and common secret fields are sanitized at result
+boundaries. This is not a universal PII detector: arbitrary private free text,
+path identifiers and unrecognized business fields may remain. Treat minimized
+reports as sensitive too.
+
+To report a vulnerability in GrantTrace itself, use GitHub's
+[private vulnerability report form](https://github.com/ysc070528/granttrace/security/advisories/new).
+Describe the affected version, reproduction steps, impact, and a minimal
+redacted example. Do not include real credentials or target data. If the form is
+unavailable to your account, ask the owner for a private contact channel without
+disclosing vulnerability details in a public issue.
+