ci: apply security best practices

[stepsecurity-int]

Summary

This pull request has been generated by StepSecurity as part of your enterprise subscription to ensure compliance with recommended security best practices. Please review and merge the pull request to apply these security enhancements.

Security Fixes

Pinned Dependencies

Pinning GitHub Actions to specific versions or commit SHAs ensures that your workflows remain consistent and secure.
Unpinned actions can lead to unexpected changes or vulnerabilities caused by upstream updates.

• GitHub Security Guide
• The Open Source Security Foundation (OpenSSF) Security Guide

Feedback

email here

[step-security-bot]

Please find StepSecurity AI-CodeWise code comments below.

Code Comments

.github/workflows/create_review.yml

[
    {
        "Severity": "High",
        "Recommendation": "Avoid using direct dependencies on specific commit hashes for external libraries or tools.",
        "Description": "Depending on specific commit hashes can lead to potential issues with reproducibility, maintainability, and security.",
        "Remediation": "Update the dependency to use a specific version tag or range instead of a commit hash."
    },
    {
        "Severity": "Medium",
        "Recommendation": "Ensure consistent and secure vetting of third-party GitHub Actions used in the workflow.",
        "Description": "Using third-party actions without proper vetting can introduce security risks and potential vulnerabilities.",
        "Remediation": "Review the source code and permissions of the third-party action being added, and consider using verified actions from official sources."
    }
]

Feedback

We appreciate your feedback in helping us improve the service! To provide feedback, please use emojis on this comment. If you find the comments helpful, give them a 👍. If they aren't useful, kindly express that with a 👎. If you have questions or detailed feedback, please create n GitHub issue in StepSecurity/AI-CodeWise.