Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(StepSecurity): Apply security best practices #86

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

step-security-bot
Copy link

Summary

This pull request is created by StepSecurity at the request of @mehmeteminkartal. Please merge the Pull Request to incorporate the requested changes. Please tag @mehmeteminkartal on your message if you have any questions related to the PR.

Security Fixes

Pinned Dependencies

GitHub Action tags and Docker tags are mutable. This poses a security risk. GitHub's Security Hardening guide recommends pinning actions to full length commit.

Harden Runner

Harden-Runner is an open-source security agent for the GitHub-hosted runner to prevent software supply chain attacks. It prevents exfiltration of credentials, detects tampering of source code during build, and enables running jobs without sudo access.

Harden runner usage

You can find link to view insights and policy recommendation in the build log

Please refer to documentation to find more details.

Keeping your actions up to date with Dependabot

With Dependabot version updates, when Dependabot identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. This is recommended by GitHub as well as The Open Source Security Foundation (OpenSSF).

Maintain Code Quality with Pre-Commit

Pre-commit is a framework for managing and maintaining multi-language pre-commit hooks. Hooks can be any scripts, code, or binaries that run at any stage of the git workflow. Pre-commit hooks are useful for enforcing code quality, code formatting, and detecting security vulnerabilities.

Feedback

For bug reports, feature requests, and general feedback; please email support@stepsecurity.io. To create such PRs, please visit https://app.stepsecurity.io/securerepo.

Signed-off-by: StepSecurity Bot bot@stepsecurity.io

Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
Copy link

github-actions bot commented Jul 2, 2024

Coverage report

St.
Category Percentage Covered / Total
🟢 Statements 95.59% 130/136
🟢 Branches 91.67% 11/12
🟢 Functions 96.97% 32/33
🟢 Lines 95.24% 120/126

Test suite run success

18 tests passing in 4 suites.

Report generated by 🧪jest coverage report action from 1665c66

@mehmeteminkartal mehmeteminkartal changed the title [StepSecurity] Apply security best practices chore(StepSecurity): Apply security best practices Jul 2, 2024
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