[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 security and code-quality workflows recommended by StepSecurity to bring the repository in line with security best practices. The repository gains dependency review, vulnerability scanning, supply-chain scoring, and lint/format enforcement.

• Dependency Review runs on PRs and flags vulnerable or malicious dependencies, configurable via reusable workflow inputs.
• OSV Scanner workflows scan bun.lock, compare PR branches against the base branch for new vulnerabilities, and upload SARIF results to code scanning.
• Scorecard assesses supply-chain security on the default branch and PRs, and can publish results to the OpenSSF REST API.
• Lint and Format checks Prettier, markdownlint, and actionlint on changed Markdown, YAML, JSON, and lockfile paths.
• All workflows use step-security/harden-runner with egress audit and pin actions to commit SHAs.

^{Written for commit ebaa2f0. 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.