[StepSecurity] Apply security best practices

[stepsecurity-app]

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 recommended security workflows this repository was missing, as generated by StepSecurity. No existing CI behavior changes; the new workflows run alongside current automation.

New Features

• dependency-review-reusable.yml runs GitHub dependency review with a configurable severity threshold and PR summary comments.
• lint-and-format.yml enforces Prettier, markdownlint, and actionlint checks on PRs touching markdown, workflow, or config files and on pushes to main.
• osv-scanner-full-reusable.yml and osv-scanner-pr-reusable.yml scan dependencies for known vulnerabilities and upload SARIF results to code scanning; the PR variant blocks PRs that introduce new vulnerabilities.
• osv-scanner-smoke.yml runs the scanner against bun.lock on PRs and on manual dispatch.
• scorecard-reusable.yml runs the OpenSSF Scorecard supply-chain analysis and uploads the SARIF results.

^{Written for commit 9bfef95. Summary will update on new commits.}

[github-advanced-security]

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.