Skip to content

[codex] sbom-diff-and-risk v0.3.0 - #9

Merged
stacknil merged 2 commits into
mainfrom
codex/sbom-diff-risk-v0.3.0
Apr 19, 2026
Merged

stacknil merged 2 commits into
mainfrom
codex/sbom-diff-risk-v0.3.0

Conversation

@stacknil

Copy link
Copy Markdown
Owner

Summary

  • prepare sbom-diff-and-risk for the v0.3.0 release
  • add opt-in PyPI provenance enrichment
  • add provenance-aware policy
  • add provenance-aware report and SARIF behavior
  • add self-provenance verification for workflow-built artifacts
  • bump package metadata to 0.3.0 and make SARIF golden tests path-stable across environments

Validation

  • pytest

@stacknil
stacknil merged commit 159613e into main Apr 19, 2026
6 checks passed
@stacknil
stacknil deleted the codex/sbom-diff-risk-v0.3.0 branch April 19, 2026 10:03

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6fb90f5cab

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +247 to +251
if not isinstance(value, (int, float)):
raise PolicyError(f"Invalid policy schema in {context}: expected a number between 0 and 10.")
normalized = float(value)
if normalized < 0 or normalized > 10:
raise PolicyError(f"Invalid policy schema in {context}: expected a number between 0 and 10.")

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Reject boolean and NaN scorecard thresholds

minimum_scorecard_score currently accepts any int/float, so YAML values like true (treated as 1.0) and .nan pass validation; .nan in particular bypasses the range check and then makes every scored component look below threshold because comparisons against NaN are always false. This can silently turn a misconfigured policy into widespread false violations, so parsing should explicitly reject booleans and non-finite floats.

Useful? React with 👍 / 👎.

@stacknil

Copy link
Copy Markdown
Owner Author

Opened follow-up PR #10 to address the minimum_scorecard_score review issue. It rejects YAML booleans and non-finite values (.nan, .inf, -.inf) at parse time and adds regression tests for those cases.

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