Skip to content

docs: list TRUSTABL_FINDINGS_COUNT among the trustabl.env outputs - #30

Open
bradAGI wants to merge 1 commit into
trustabl:mainfrom
bradAGI:docs/list-findings-count-output
Open

docs: list TRUSTABL_FINDINGS_COUNT among the trustabl.env outputs#30
bradAGI wants to merge 1 commit into
trustabl:mainfrom
bradAGI:docs/list-findings-count-output

Conversation

@bradAGI

@bradAGI bradAGI commented Aug 24, 2026

Copy link
Copy Markdown

The scanner writes five variables to trustabl.env; docs/EVALUATION.md names four.

$ grep -n 'echo "TRUSTABL_' scan/trustabl-scan.sh
161:  echo "TRUSTABL_EXIT_CODE=$NATIVE_CODE"
162:  echo "TRUSTABL_READINESS_SCORE=$SCORE"
163:  echo "TRUSTABL_RISK_SCORE=$RISK"
164:  echo "TRUSTABL_MAX_SEVERITY=$MAX_SEV"
165:  echo "TRUSTABL_FINDINGS_COUNT=$COUNT"

vs the guide:

trustabl.env exposes TRUSTABL_EXIT_CODE, TRUSTABL_READINESS_SCORE, TRUSTABL_RISK_SCORE and TRUSTABL_MAX_SEVERITY for downstream steps.

The root README's Outputs section already lists all five, so the guide is the one out of step.

Worth fixing rather than leaving: findings count is the variable a downstream step is most likely to want — a badge, a Slack summary, a Security Hub import — because the other four describe the gate's decision rather than what was actually found. Someone reading only the evaluation guide would not know it is there.

One-line docs change.

The scanner writes five variables; the evaluation guide names four.

  scan/trustabl-scan.sh:161  TRUSTABL_EXIT_CODE
  scan/trustabl-scan.sh:162  TRUSTABL_READINESS_SCORE
  scan/trustabl-scan.sh:163  TRUSTABL_RISK_SCORE
  scan/trustabl-scan.sh:164  TRUSTABL_MAX_SEVERITY
  scan/trustabl-scan.sh:165  TRUSTABL_FINDINGS_COUNT   <- undocumented here

The root README's Outputs section already lists all five, so the guide was the
one out of step. Findings count is also the variable a downstream step is most
likely to reach for — a badge, a Slack line, a Security Hub import — since the
other four describe the gate rather than what it found.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant