Skip to content

Add weekly OSV-Scanner vulnerability scans - #174

Merged
JaredHatfield merged 5 commits into
mainfrom
security/add-osv-scanner
Oct 24, 2026
Merged

JaredHatfield merged 5 commits into
mainfrom
security/add-osv-scanner

Conversation

@JaredHatfield

Copy link
Copy Markdown
Member

Add OSV-Scanner source dependency scans for pull requests, default-branch pushes, manual runs, and Sundays at 09:23 UTC. Google's official reusable workflows are pinned to b1d267aea5211fa648d9d442fa64b90dbdcbdd36, the commit behind release v2.7.0.

Findings are report-only during the initial rollout; scanner failures still fail the job. Recursive scanning covers supported manifests and lockfiles. Repositories with no supported dependency files produce empty results.

SARIF is uploaded to GitHub code scanning and preserved as Actions artifacts.

Weekly and manual runs also scan published container images on native amd64 and arm64 runners. Images are exported to archives for scanning, without rebuilding or running application containers. Image JSON and SARIF reports are retained for 30 days.

Images:

  • ghcr.io/unitvectory-labs/gcpmetadataexplorer-snapshot:dev

Generated from the companion uvy-labs-gitrepoforge template change. Only the new workflow and its .managedfiles entry are included. Existing Go scans and unrelated gitrepoforge drift are preserved.

Validation: actionlint and offline zizmor pass. The release tag was resolved through GitHub's Git API. Managed outputs were rendered and validated with gitrepoforge; each final diff was restricted to the scanner addition and corresponding manifest entry. Application code was not changed.
Published image manifests were checked for both target architectures without downloading image layers.

OSV-Scanner GitHub Action documentation

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

@codecov

codecov Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (47d8fbb) to head (4142e6b).

Additional details and impacted files
@@          Coverage Diff          @@
##            main    #174   +/-   ##
=====================================
  Coverage   0.00%   0.00%           
=====================================
  Files          1       1           
  Lines        330     330           
=====================================
  Misses       330     330           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@JaredHatfield
JaredHatfield enabled auto-merge (squash) October 24, 2026 15:33
@JaredHatfield
JaredHatfield merged commit 2292c03 into main Oct 24, 2026
11 checks passed
@JaredHatfield
JaredHatfield deleted the security/add-osv-scanner branch October 24, 2026 15:38
@github-project-automation github-project-automation Bot moved this from Todo to Done in UnitVectorY Labs Oct 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants