feat: Apply security best practices

[step-security-bot]

Summary

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

Security Fixes

Least Privileged GitHub Actions Token Permissions

The GITHUB_TOKEN is an automatically generated secret to make authenticated calls to the GitHub API. GitHub recommends setting minimum token permissions for the GITHUB_TOKEN.

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

Add Dependency Review Workflow

The Dependency Review Workflow enforces dependency reviews on your pull requests. The action scans for vulnerable versions of dependencies introduced by package version changes in pull requests, and warns you about the associated security vulnerabilities. This gives you better visibility of what's changing in a pull request, and helps prevent vulnerabilities being added to your repository.

• Github Guide about Dependency Review
• Github Guide for Configuring Dependency Review Action

Add OpenSSF Scorecard Workflow

OpenSSF Scorecard is an automated tool that assesses a number of important heuristics ("checks") associated with software security and assigns each check a score of 0-10. You can use these scores to understand specific areas to improve in order to strengthen the security posture of your project.

Scorecard workflow also allows maintainers to display a Scorecard badge on their repository to show off their hard work.

• The Open Source Security Foundation (OpenSSF) Scorecard

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.

• Official Pre-commit documentation
• Getting Started guide

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

---

Summary by cubic

Hardened CI by enforcing least-privilege tokens, adding PR dependency review and OpenSSF Scorecard, and introducing .pre-commit hooks. Also formatted workflow YAML (no behavior change) and removed CodeQL and Dependabot updates for now.

• New Features
  • Set permissions: contents: read across build, test, release, and maintenance workflows.
  • Added actions/dependency-review-action on PRs (fails on high severity; comments a summary).
  • Added ossf/scorecard-action on a weekly schedule and on pushes to main; uploads SARIF to code scanning.
  • Introduced .pre-commit hooks for secrets and linting.

^{Written for commit 2a7cf61. Summary will update on new commits. Review in cubic}

[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.