Merged
Conversation
…s in release workflow
…rsioning in backend workflow
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces several improvements to CI/CD security and transparency, as well as documentation and marketing enhancements. The most significant changes are the addition of new security scanning workflows, pinning of GitHub Action versions for supply chain security, and the introduction of a comprehensive marketing plan. Below are the key changes grouped by theme:
Security and Compliance Enhancements:
.github/workflows/security.ymlworkflow to rungovulncheckandgosecstatic analysis on Go code for vulnerability and security scanning on each push and pull request..gosec.yamlconfiguration file to customizegosecscanning, including suppressing a known false positive for zip-slip in theinternal/generatorpackage.CI/CD Supply Chain Hardening:
backend.yml,frontend.yml,release.yml,security.yml) to specific commit SHAs instead of floating version tags, reducing the risk of supply chain attacks. [1] [2] [3] [4] [5] [6] [7] [8] [9]Documentation and Project Management:
PLAN.mdoutlining the project's marketing strategy, growth phases, content plan, and metrics for tracking success.Developer Tooling:
Makefiletarget (update-digests) to automate checking and updating Docker image digests for base images, improving reproducibility and security of Docker builds.Workflow Permissions Tightening:
permissions: {}orcontents: read) in all GitHub Actions workflows to follow the principle of least privilege. [1] [2] [3] [4] [5] [6] [7]These changes collectively improve the project's security posture, transparency, and readiness for broader adoption and contribution.