Skip to content

[StepSecurity] Apply security best practices - #1

Open
stepsecurity-app[bot] wants to merge 1 commit into
mainfrom
chore/GHA-281421-stepsecurity-remediation
Open

stepsecurity-app[bot] wants to merge 1 commit into
mainfrom
chore/GHA-281421-stepsecurity-remediation

Conversation

@stepsecurity-app

@stepsecurity-app stepsecurity-app Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

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

Recommended GitHub Actions Workflows

These workflows are part of the organization's recommended set and were previously missing from this repository.

Feedback

For bug reports, feature requests, and general feedback; please create an issue in step-security/secure-repo or contact us via our website.


Summary by cubic

Adds the organization's recommended security workflows so dependency review, vulnerability scanning, scorecard, and lint/format checks run on pull requests and the main branch.

New Features

  • Dependency Review blocks PRs when dependencies exceed the configured severity threshold.
  • OSV scanner checks bun.lock for vulnerabilities on PRs and the main branch, failing on new findings and uploading SARIF results to code scanning.
  • Scorecard runs on a schedule and on pushes to main, publishing results for public badge and code scanning.
  • Lint and Format runs Prettier, markdownlint, and actionlint on changed files.

Written for commit 721c96e. Summary will update on new commits.

Review in cubic

Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
@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.

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