You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi python-docx Maintainers,
As open-source security is a growing concern, I'd like to suggest some improvements based on the OpenSSF Scorecard best practices:
• Token Permissions: Consider implementing explicit token permissions within the workflow to avoid over-permissioning vulnerabilities.
• Branch Protection & Code Review: Enabling branch protection rules and code reviews can minimize the risk of introducing vulnerabilities. Refer to your repository settings for configuration options.
• Static Application Security Testing (SAST): Implementing SAST tools can help detect vulnerabilities early in the development lifecycle.
• Dependency Update Tool: Utilizing a dependency update tool ensures your project uses the latest secure library versions.
• Security Policy: Defining a comprehensive security policy (SECURITY.md) with vulnerability reporting guidelines, coding standards, and response procedures is recommended.
• Packaging:Build and release official packages using the CI/CD pipeline.
• Code Review:Perform manual review before code merging.
For more information on specific checks, see the OpenSSF Scorecard documentation: Link to Documentation
The text was updated successfully, but these errors were encountered:
Hi python-docx Maintainers,
As open-source security is a growing concern, I'd like to suggest some improvements based on the OpenSSF Scorecard best practices:
• Token Permissions: Consider implementing explicit token permissions within the workflow to avoid over-permissioning vulnerabilities.
• Branch Protection & Code Review: Enabling branch protection rules and code reviews can minimize the risk of introducing vulnerabilities. Refer to your repository settings for configuration options.
• Static Application Security Testing (SAST): Implementing SAST tools can help detect vulnerabilities early in the development lifecycle.
• Dependency Update Tool: Utilizing a dependency update tool ensures your project uses the latest secure library versions.
• Security Policy: Defining a comprehensive security policy (SECURITY.md) with vulnerability reporting guidelines, coding standards, and response procedures is recommended.
• Packaging:Build and release official packages using the CI/CD pipeline.
• Code Review:Perform manual review before code merging.
For more information on specific checks, see the OpenSSF Scorecard documentation: Link to Documentation
The text was updated successfully, but these errors were encountered: