ai-saas-guard 0.27.0 → 0.27.2

package/CONTRIBUTING.md

@@ -7,7 +7,7 @@
 1. Open an issue or comment on an existing issue before large feature work.
 2. Keep pull requests focused. Separate scanner behavior, docs, workflow changes, and release work when practical.
 3. Include tests for behavior changes. New scanner rules need a vulnerable fixture, a safe fixture, and assertions for both.
-4. Update documentation when behavior, commands, outputs, or release expectations change. If `README.md` changes, review and update `README.zh-CN.md` in the same pull request.
+4. Update documentation when behavior, commands, outputs, or release expectations change. If `README.md` changes, review and update `docs/README.zh-CN.md` in the same pull request.
 5. Fill out the pull request template with release gate evidence and known limitations.
 
 ## Local Development

package/README.md

@@ -13,7 +13,7 @@
 </p>
 
 <p align="center">
-  English | <a href="README.zh-CN.md">中文 README</a>
+  English | <a href="docs/README.zh-CN.md">中文 README</a>
 </p>
 
 <p align="center">
@@ -73,13 +73,13 @@ The CLI is published on npm as `ai-saas-guard`, and the GitHub Action is availab
 | Area | Status |
 | --- | --- |
 | Public GitHub repository | Available |
-| npm CLI | `ai-saas-guard@0.27.0` |
-| GitHub Action | `zr9959/ai-saas-guard@v0` or fixed tag `v0.27.0` |
+| npm CLI | `ai-saas-guard@0.27.2` |
+| GitHub Action | `zr9959/ai-saas-guard@v0` or fixed tag `v0.27.2` |
 | Outputs | Terminal, JSON, SARIF, and PR-focused markdown |
 | Project config | `.ai-saas-guard.json` rule toggles, severity overrides, suppressions, and fail thresholds |
 | Privacy model | Local-first, read-only scan commands, no LLM calls, no code upload |
-| Versioned Action tags | `v0.27.0`, `v0` |
-| Current release | `0.27.0` launch-gate report summary for CLI and hosted Check Runs |
+| Versioned Action tags | `v0.27.2`, `v0` |
+| Current release | `0.27.2` npm README metadata fix; launch-gate report summary remains current |
 | npm publishing | Trusted Publisher/OIDC, no long-lived publish token |
 | Repository trust hardening | Strict branch protection, Dependabot, CodeQL, fast-check fuzzing, signed release provenance assets, private vulnerability reporting, secret scanning, and push protection |
 | Cloudflare hosted ingress | Deployed at `https://ai-saas-guard-hosted.zr9959.workers.dev`; Worker health and Check Run publisher configuration are live, but end-to-end GitHub App webhook delivery is still blocked pending private App settings verification |
@@ -294,7 +294,7 @@ Use `suppressions` for narrower false-positive handling when one rule is noisy o
 
 ## GitHub Action
 
-The repo includes a composite Action. Use `v0` for the latest compatible pre-1.0 Action, a specific release tag such as `v0.27.0` for controlled upgrades, or pin a reviewed commit SHA for stricter supply-chain control:
+The repo includes a composite Action. Use `v0` for the latest compatible pre-1.0 Action, a specific release tag such as `v0.27.2` for controlled upgrades, or pin a reviewed commit SHA for stricter supply-chain control:
 
 ```yaml
 name: ai-saas-guard

package/{README.zh-CN.md → docs/README.zh-CN.md}

@@ -13,15 +13,15 @@
 </p>
 
 <p align="center">
-  <a href="README.md">English README</a> | 中文
+  <a href="../README.md">English README</a> | 中文
 </p>
 
 <p align="center">
   <a href="https://github.com/zr9959/ai-saas-guard/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/zr9959/ai-saas-guard/actions/workflows/ci.yml/badge.svg"></a>
   <a href="https://www.bestpractices.dev/projects/12955"><img alt="OpenSSF Best Practices" src="https://www.bestpractices.dev/projects/12955/badge"></a>
   <a href="https://www.npmjs.com/package/ai-saas-guard"><img alt="npm" src="https://img.shields.io/npm/v/ai-saas-guard.svg"></a>
-  <a href="LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/license-MIT-blue.svg"></a>
-  <a href="package.json"><img alt="Node.js >=20" src="https://img.shields.io/badge/node-%3E%3D20-339933.svg"></a>
+  <a href="../LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/license-MIT-blue.svg"></a>
+  <a href="../package.json"><img alt="Node.js >=20" src="https://img.shields.io/badge/node-%3E%3D20-339933.svg"></a>
 </p>
 
 ---
@@ -67,22 +67,22 @@ AI 能很快把一个 SaaS 做到“看起来能用”。真正危险的是上
 
 这个仓库是公开 GitHub 仓库。
 
-CLI 已发布到 npm：`ai-saas-guard@0.27.0`。GitHub Action 支持 `v0` 浮动标签，也支持固定版本标签，例如 `v0.27.0`。
+CLI 已发布到 npm：`ai-saas-guard@0.27.2`。GitHub Action 支持 `v0` 浮动标签，也支持固定版本标签，例如 `v0.27.2`。
 
 | 模块 | 状态 |
 | --- | --- |
 | 公开 GitHub 仓库 | 已可用 |
-| npm CLI | `ai-saas-guard@0.27.0` |
-| GitHub Action | `zr9959/ai-saas-guard@v0` 或固定标签 `v0.27.0` |
+| npm CLI | `ai-saas-guard@0.27.2` |
+| GitHub Action | `zr9959/ai-saas-guard@v0` 或固定标签 `v0.27.2` |
 | 输出格式 | Terminal、JSON、SARIF 和 PR markdown |
 | 项目配置 | `.ai-saas-guard.json` 支持规则开关、severity 覆盖、suppressions 和 fail threshold |
 | 隐私模型 | 本地优先、只读扫描、不调用 LLM、不上传代码 |
-| 当前版本 | `0.27.0` CLI 和 hosted Check Run 的 launch-gate report summary |
-| Action 标签 | `v0.27.0`、`v0` |
+| 当前版本 | `0.27.2` npm README metadata fix；CLI 和 hosted Check Run 的 launch-gate report summary 仍是当前功能 |
+| Action 标签 | `v0.27.2`、`v0` |
 | npm 发布 | GitHub Actions Trusted Publisher/OIDC，无需长期 npm token |
 | 仓库可信度加固 | 严格 branch protection、Dependabot、CodeQL、fast-check fuzzing、signed release provenance assets、private vulnerability reporting、secret scanning 和 push protection |
 | Cloudflare hosted ingress | 已部署到 `https://ai-saas-guard-hosted.zr9959.workers.dev`；Worker health 和 Check Run publisher 配置已在线，但端到端 GitHub App webhook delivery 仍需要验证私有 App 设置 |
-| Hosted GitHub App staging | 私有 App `ai-saas-guard-hosted`（`3834787`）已安装到 `zr9959/ai-saas-guard`；hosted operations evidence 见 [docs/hosted-operations-evidence.md](docs/hosted-operations-evidence.md) |
+| Hosted GitHub App staging | 私有 App `ai-saas-guard-hosted`（`3834787`）已安装到 `zr9959/ai-saas-guard`；hosted operations evidence 见 [docs/hosted-operations-evidence.md](hosted-operations-evidence.md) |
 | OpenSSF Best Practices | 已获得 passing badge，项目 `12955`；`.bestpractices.json` 继续作为保守证据记录 |
 
 ## 快速开始
@@ -148,17 +148,17 @@ node dist/cli.js scan --root /path/to/your-saas
 | GitHub Actions | workflow 权限过宽、PR workflow 缺 concurrency cancel、docs-only 改动跑全量 CI、secret/tool version 缺 fail-fast、`pr-risk` checkout 太浅、Action 未 pin SHA |
 | PR risk | auth、billing、RLS、env、deploy、API、storage、silent-success、测试删除、缺 spec/context、大型混合 diff |
 
-完整规则请看 [docs/rules.md](docs/rules.md)。
+完整规则请看 [docs/rules.md](rules.md)。
 
 ## 仓库可信度加固
 
-公开仓库的维护和发布控制见 [docs/repository-trust-hardening.md](docs/repository-trust-hardening.md)。当前已经配置严格 branch protection、required CI checks、Dependabot npm/GitHub Actions 更新、CodeQL SAST、fast-check fuzz/property tests、基于 npm trusted publishing provenance 的 signed GitHub release assets、private vulnerability reporting、secret scanning 和 push protection。
+公开仓库的维护和发布控制见 [docs/repository-trust-hardening.md](repository-trust-hardening.md)。当前已经配置严格 branch protection、required CI checks、Dependabot npm/GitHub Actions 更新、CodeQL SAST、fast-check fuzz/property tests、基于 npm trusted publishing provenance 的 signed GitHub release assets、private vulnerability reporting、secret scanning 和 push protection。
 
 最新 GitHub releases 会镜像 npm package tarball，并附带 `*.tgz.sigstore.json` 和 `*.tgz.intoto.jsonl` provenance assets。上传前会用 npm registry metadata 校验 tarball digest，并使用 npm provenance 作为来源。
 
 当前 Scorecard 提升路线优先做真实控制，不做表面刷分：更严格的 review gate、可被检测到的 fuzzing、以及 OpenSSF Best Practices Badge 流程。仓库年龄、贡献者多样性、已 review 的 PR 历史这些分数只能随着真实维护逐步提升。
 
-仓库现在已经获得 [OpenSSF Best Practices passing badge](https://www.bestpractices.dev/projects/12955)。[.bestpractices.json](.bestpractices.json) 继续作为公开项目条目的保守证据记录。`dynamic_analysis_enable_assertions` 仍然谨慎标为 unmet，直到运行时断言覆盖面超过当前测试、property 和 fuzz assertions。
+仓库现在已经获得 [OpenSSF Best Practices passing badge](https://www.bestpractices.dev/projects/12955)。[.bestpractices.json](../.bestpractices.json) 继续作为公开项目条目的保守证据记录。`dynamic_analysis_enable_assertions` 仍然谨慎标为 unmet，直到运行时断言覆盖面超过当前测试、property 和 fuzz assertions。
 
 ## PR 风险分流
 
@@ -229,7 +229,7 @@ jobs:
           config: .ai-saas-guard.json
 ```
 
-更多 GitHub Action 示例请看 [docs/github-action.md](docs/github-action.md)。
+更多 GitHub Action 示例请看 [docs/github-action.md](github-action.md)。
 
 ## 项目配置
 
@@ -270,23 +270,23 @@ jobs:
 
 ## Hosted GitHub App 设计
 
-当前仓库已经包含未来 Hosted GitHub App 的设计文档、纯契约测试，以及第一个真实 Cloudflare hosted ingress。私有 staging GitHub App `ai-saas-guard-hosted` 已安装到 `zr9959/ai-saas-guard`，Cloudflare 已配置所需的云端凭据绑定。Worker 代码已经能接收签名 webhook、写入 KV 队列、换取 scoped installation token、读取 GitHub PR file metadata、做 compact PR-risk classification，并发布有长度上限的 Check Run summary；但当前端到端 GitHub App webhook delivery smoke 还被私有 App webhook 设置阻断，证据记录在 [docs/hosted-operations-evidence.md](docs/hosted-operations-evidence.md)。它还不是完整 source checkout scan worker。
+当前仓库已经包含未来 Hosted GitHub App 的设计文档、纯契约测试，以及第一个真实 Cloudflare hosted ingress。私有 staging GitHub App `ai-saas-guard-hosted` 已安装到 `zr9959/ai-saas-guard`，Cloudflare 已配置所需的云端凭据绑定。Worker 代码已经能接收签名 webhook、写入 KV 队列、换取 scoped installation token、读取 GitHub PR file metadata、做 compact PR-risk classification，并发布有长度上限的 Check Run summary；但当前端到端 GitHub App webhook delivery smoke 还被私有 App webhook 设置阻断，证据记录在 [docs/hosted-operations-evidence.md](hosted-operations-evidence.md)。它还不是完整 source checkout scan worker。
 
 相关文档：
 
-- [docs/github-app-design.md](docs/github-app-design.md)
-- [docs/github-app-deployment.md](docs/github-app-deployment.md)
-- [docs/hosted-first-service-slice.md](docs/hosted-first-service-slice.md)
-- [docs/hosted-deployment-model.md](docs/hosted-deployment-model.md)
-- [docs/hosted-service-runtime.md](docs/hosted-service-runtime.md)
-- [docs/hosted-production-adapters.md](docs/hosted-production-adapters.md)
-- [docs/hosted-node-container-app.md](docs/hosted-node-container-app.md)
-- [docs/hosted-staging-deployment.md](docs/hosted-staging-deployment.md)
-- [docs/hosted-staging-harness.md](docs/hosted-staging-harness.md)
-- [docs/hosted-operational-release-gate.md](docs/hosted-operational-release-gate.md)
-- [docs/hosted-uninstall-data-deletion.md](docs/hosted-uninstall-data-deletion.md)
-- [docs/hosted-pricing-packaging.md](docs/hosted-pricing-packaging.md)
-- [docs/hosted-preimplementation-contracts.md](docs/hosted-preimplementation-contracts.md)
+- [docs/github-app-design.md](github-app-design.md)
+- [docs/github-app-deployment.md](github-app-deployment.md)
+- [docs/hosted-first-service-slice.md](hosted-first-service-slice.md)
+- [docs/hosted-deployment-model.md](hosted-deployment-model.md)
+- [docs/hosted-service-runtime.md](hosted-service-runtime.md)
+- [docs/hosted-production-adapters.md](hosted-production-adapters.md)
+- [docs/hosted-node-container-app.md](hosted-node-container-app.md)
+- [docs/hosted-staging-deployment.md](hosted-staging-deployment.md)
+- [docs/hosted-staging-harness.md](hosted-staging-harness.md)
+- [docs/hosted-operational-release-gate.md](hosted-operational-release-gate.md)
+- [docs/hosted-uninstall-data-deletion.md](hosted-uninstall-data-deletion.md)
+- [docs/hosted-pricing-packaging.md](hosted-pricing-packaging.md)
+- [docs/hosted-preimplementation-contracts.md](hosted-preimplementation-contracts.md)
 
 已经实现的 hosted 预实现纯契约包括：
 
@@ -307,7 +307,7 @@ jobs:
 - worker checkout cleanup planner
 - retention/deletion cleanup planner：把 compact report 删除、按仓库或 installation 范围取消队列和 running job、worker checkout 删除、retention 过期清理、最小审计记录合成一个安全计划；不会输出源码、diff、secret、customer payload、private URL、checkout path 或底层 cleanup error
 - operational release gate evaluator：检查 hosted 暴露前是否具备 fresh CI、webhook replay、workflow static check、dependency/container scan、cleanup、privacy、monitoring、rollback、incident response 和 release cleanup 证据；缺任何 P0 证据都会阻止 hosted exposure
-- hosted compact report fixture：[examples/hosted-compact-report.json](examples/hosted-compact-report.json)
+- hosted compact report fixture：[examples/hosted-compact-report.json](../examples/hosted-compact-report.json)
 
 这些 helper 不会暴露公开服务、不会直接调用 GitHub API、不会持久化 installation token、不会真实写 check run、不会发 PR comment，也不会上传源码。
 
@@ -334,12 +334,12 @@ npm run build
 node dist/cli.js scan --root .
 ```
 
-发布 CLI、GitHub Action、npm package 或任何公开仓库更新前，必须按照 [docs/release-quality-knowledge-base.md](docs/release-quality-knowledge-base.md) 的 release gate 执行。
+发布 CLI、GitHub Action、npm package 或任何公开仓库更新前，必须按照 [docs/release-quality-knowledge-base.md](release-quality-knowledge-base.md) 的 release gate 执行。
 
-以后更新英文 `README.md` 时，也要同步检查并更新本中文 `README.zh-CN.md`。
+以后更新英文 `README.md` 时，也要同步检查并更新本中文 `docs/README.zh-CN.md`。
 
-贡献要求见 [CONTRIBUTING.md](CONTRIBUTING.md)，里面说明了 PR 流程、测试要求、规则设计、release gate evidence 和公开安全边界。
+贡献要求见 [CONTRIBUTING.md](../CONTRIBUTING.md)，里面说明了 PR 流程、测试要求、规则设计、release gate evidence 和公开安全边界。
 
 ## 安全报告
 
-报告漏洞前请阅读 [SECURITY.md](SECURITY.md)。不要在公开 issue 中发布真实 API key、客户数据、私有源码或生产 URL。
+报告漏洞前请阅读 [SECURITY.md](../SECURITY.md)。不要在公开 issue 中发布真实 API key、客户数据、私有源码或生产 URL。

package/docs/github-action.md

@@ -2,7 +2,7 @@
 
 `ai-saas-guard` ships as a composite GitHub Action for pull request and code scanning workflows.
 
-Use `zr9959/ai-saas-guard@v0` for the latest compatible pre-1.0 Action. Use a specific tag such as `v0.27.0` or a reviewed commit SHA when reproducibility is more important than automatic minor updates.
+Use `zr9959/ai-saas-guard@v0` for the latest compatible pre-1.0 Action. Use a specific tag such as `v0.27.2` or a reviewed commit SHA when reproducibility is more important than automatic minor updates.
 
 ## PR Summary
 

package/docs/npm-publishing.md

@@ -5,11 +5,11 @@
 ## Current State
 
 - Package name: `ai-saas-guard`
-- Current published version: `0.27.0`
+- Current published version: `0.27.2`
 - Next source candidate: none
 - npm registry state: published at <https://www.npmjs.com/package/ai-saas-guard>
 - First npm-published version: `0.1.1`
-- GitHub Release: `v0.27.0`
+- GitHub Release: `v0.27.2`
 - Publish workflow: `.github/workflows/npm-publish.yml`
 - Trusted Publisher: GitHub Actions, `zr9959/ai-saas-guard`, workflow `npm-publish.yml`, allowed action `npm publish`
 - Long-lived npm publish token: not required
@@ -18,7 +18,7 @@
 
 Use GitHub Actions with npm Trusted Publisher/OIDC:
 
-1. Create and review a release tag such as `v0.27.0`.
+1. Create and review a release tag such as `v0.27.2`.
 2. Publish from the GitHub Release or run the `Publish npm` workflow manually with `ref` set to that tag.
 3. Keep `permissions.id-token: write` in the workflow so npm can exchange the GitHub Actions OIDC identity for a short-lived publish credential.
 4. Run `npm publish --access public` from the workflow. Trusted publishing automatically generates provenance for this public package from this public repository.

package/docs/project-handoff.md

@@ -160,7 +160,7 @@ OpenSSF Best Practices:
 Publishing:
 
 - npm package: `ai-saas-guard`
-- Current published release line: `v0.27.0`
+- Current published release line: `v0.27.2`
 - Next source candidate: none
 - Publish workflow: `.github/workflows/npm-publish.yml`
 - Trusted Publisher: GitHub Actions for `zr9959/ai-saas-guard`, workflow `npm-publish.yml`
@@ -173,7 +173,7 @@ Allowed in this public repository:
 - CLI source code
 - tests and intentionally vulnerable fixtures
 - public docs
-- English README and Chinese README; when `README.md` changes, review and update `README.zh-CN.md` in the same change
+- English README and Chinese README; when `README.md` changes, review and update `docs/README.zh-CN.md` in the same change
 - GitHub Action wrapper
 - examples that contain only inert fake data
 - release-quality process docs

package/docs/release-quality-knowledge-base.md

@@ -235,7 +235,7 @@ P0:
 - `types` points to generated declaration files if package exports TypeScript API.
 - `exports` is accurate.
 - README install examples match the published package name.
-- If `README.md` changes, `README.zh-CN.md` must be reviewed and updated or explicitly confirmed still current.
+- If `README.md` changes, `docs/README.zh-CN.md` must be reviewed and updated or explicitly confirmed still current.
 - Version follows semver.
 - Release notes state breaking changes, new checks, false-positive changes, and migration notes.
 - Publish with npm trusted publishing/OIDC when possible.

package/docs/repository-trust-hardening.md

@@ -125,6 +125,6 @@ The repository also includes `.bestpractices.json` with conservative proposed an
 Current badge evidence:
 
 - `CONTRIBUTING.md` documents the pull request process, test expectations, rule-design requirements, release gate evidence, and public-safety constraints.
-- `README.md` and `README.zh-CN.md` document the problem, install path, CLI commands, privacy model, GitHub Action use, hosted boundaries, and trust-hardening controls.
+- `README.md` and `docs/README.zh-CN.md` document the problem, install path, CLI commands, privacy model, GitHub Action use, hosted boundaries, and trust-hardening controls.
 - `.bestpractices.json` records only repository-backed OpenSSF Best Practices proposed answers; unknown or future claims should stay out until they can be supported by public evidence.
 - `dynamic_analysis_enable_assertions` is intentionally still marked unmet because the production CLI does not yet have broad runtime assertion coverage beyond tests, property tests, and fuzzing.

package/package.json

@@ -1,7 +1,8 @@
 {
   "name": "ai-saas-guard",
-  "version": "0.27.0",
+  "version": "0.27.2",
   "description": "Repo-local launch-readiness scanner for AI-built SaaS apps.",
+  "readmeFilename": "README.md",
   "type": "module",
   "homepage": "https://github.com/zr9959/ai-saas-guard#readme",
   "repository": {
@@ -80,8 +81,7 @@
     "dist",
     "examples",
     "hosted",
-    "README.md",
-    "README.zh-CN.md"
+    "README.md"
   ],
   "license": "MIT",
   "devDependencies": {