@base-attribution-os/github-action 0.2.2 → 0.2.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +5 -1
  2. package/action.yml +1 -1
  3. package/dist/index.cjs +684 -681
  4. package/package.json +3 -3
package/README.md CHANGED
@@ -3,7 +3,7 @@
3
3
  Scan pull requests for Base transaction paths that are missing the expected Builder Code attribution.
4
4
 
5
5
  ```yaml
6
- - uses: horn111/bao-toolkit/packages/github-action@v0.6.0
6
+ - uses: horn111/bao-toolkit/packages/github-action@v0.6.1
7
7
  with:
8
8
  builder-code: bc_example
9
9
  profile: strict
@@ -12,3 +12,7 @@ Scan pull requests for Base transaction paths that are missing the expected Buil
12
12
  The action can scan dependency-aware changed files, resolve bounded monorepo evidence, apply a baseline, emit SARIF, and expose coverage metrics as outputs. Most users should consume the repository action shown above rather than install this package from npm.
13
13
 
14
14
  [GitHub Action documentation](https://github.com/horn111/bao-toolkit/blob/main/docs/ci-validation.md) · [Issues](https://github.com/horn111/bao-toolkit/issues)
15
+
16
+ Empty scopes show coverage as unmeasured in the summary. The numeric `coverage`
17
+ output remains `100` for compatibility; check `transaction-paths` before using it.
18
+ With `fail-on-missing: true`, an empty scope fails, including changed-only scans.
package/action.yml CHANGED
@@ -50,7 +50,7 @@ outputs:
50
50
  protected-paths:
51
51
  description: "Number of paths with verified attribution evidence."
52
52
  coverage:
53
- description: "Percentage of protected transaction paths."
53
+ description: "Percentage of protected transaction paths. Check transaction-paths first: an empty scope retains 100 for compatibility but coverage is not measured."
54
54
  profile:
55
55
  description: "Scanner profile used."
56
56
  findings: