Skip to content

chore: add OpenSSF trust baseline - #5

Merged
dzeusking-dev merged 2 commits into
mainfrom
chore/openssf-trust-20260904
Sep 4, 2026
Merged

chore: add OpenSSF trust baseline#5
dzeusking-dev merged 2 commits into
mainfrom
chore/openssf-trust-20260904

Conversation

@dzeusking-dev

Copy link
Copy Markdown
Contributor

Summary

Add the repository-specific OpenSSF trust baseline without changing runtime behavior:

  • official pinned Scorecard workflow with public result publication and SARIF upload;
  • pinned CodeQL and dependency review workflows;
  • project-specific support, governance, maintainer, threat-model and trust documentation;
  • validated Security Insights v2.2.0 metadata;
  • evidence-only Best Practices / OSPS automation proposals.

Verification

  • python -m compileall csaf_check
  • python -m pytest -q (11 passed, 1 skipped because the optional real validator is not installed locally)
  • python -m build
  • actionlint 1.7.12
  • Security Insights CUE schema validation
  • diff-only gitleaks 8.30.1: no leaks
  • local documentation links resolve

Authorization And Ethics

  • This concerns the canonical public repository.
  • This keeps csaf-check read-only for v0.x.
  • This adds no third-party discovery or protected artifact retrieval.

Non-claims

This change is not a certification, does not prove the project is vulnerability-free, does not claim a SLSA or OpenSSF badge level, and does not imply OpenSSF endorsement. No README Scorecard badge is added until a public default-branch result exists.

Rollback

Revert the merge commit. No release, tag, version, secret, product behavior or external service is changed.

Signed-off-by: Bartosz Joachimiak <admin@gexiro.com>
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

Signed-off-by: Bartosz Joachimiak <262029076+dzeusking-dev@users.noreply.github.com>
@dzeusking-dev
dzeusking-dev merged commit 4156d85 into main Sep 4, 2026
11 checks passed
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.

2 participants