Bump github.com/google/osv-scalibr from 0.2.1 to 0.4.4

[dependabot]

Bumps github.com/google/osv-scalibr from 0.2.1 to 0.4.4.

Release notes

Sourced from github.com/google/osv-scalibr's releases.

v0.4.4

• New extractors: QEMU disk images, opam, Bazel Maven dependencies
• New secret detectors: Square API creds, Salesforce creds, SendGrid API key, Deno PAT, Heroku Platform API Key, npmjs Registry Access Token, Cloudfare API token
• Fixed the StoreAbsolutePath ScanConfig option to work with annotators + enrichers

v0.4.3

• New secret scanners: OpenRouter key, base64-encoded Github PATs, PayStack secret,Telegram Bot API key, Cursor API key, Elastic Cloud API key, Salesforce OAuth2 Client Credential / Access Token / Refresh Token, Mistral API Key, CircleCI Personal Access Token and Project Access Token
• New extractor: Mise tools
• New detectors: NetScaler CVE-2025-7775, Cron job privesc vulns
• New annotators: Homebrew source metadata
• More comprehensive testing for secret detectors
• Migrated extractors to use global proto for configuration
• --unsafe flag for enabling potentially unsafe plugins

v0.4.2

• New secret extractor for Bitbucket and Amazon CodeCommit git basic auth URLs
• Rust reachability annotation migrated from OSV-Scanner
• New extractor for Chocolatey packages (Windows)
• Deps.dev API usage for pomxml dependency resolution

v0.4.1

• New secret detectors: AWS access token, Recaptcha secret key, pyx v1/v2 user key, Amazon CodeCatalyst, generic JWT
• Go source reachability enrichment using Govulncheck
• Support for more assignment patterns in the .gemspec extractor
• Support for BellSoft/Alpaquita OS packages
• Fixes: Correct the COS os-duplicate annotator behavior, avoid duplicate inventories when traversing multiple ScanRoots
• Include PackageVulns in output proto

v0.4.0

• Global plugin config: Plugins can now be configured through a unified flag from the CLI and proto field from the library
  • Using e.g. --plugin-config=max_file_size_bytes:10000000 --plugin-config=go_binary:{version_from_content:true}
  • Migration for all plugins to use this setup is still in progress
  • This adds a new plugin config param to the list.go plugin initializers (list.FromNames()) and is thus a breaking change for current list.go API users
• New secret scanners: MariaDB creds, MySQL mylogin.cnf creds, VAPID keys
• Guided Remediation support for Python projects managed with Pipenv
• Enricher that adds package deprecation information: -plugins=packagedeprecation/depsdev
• Annotator for DPKG package sources: -plugins=misc/dpkg-source

v0.3.6

• New extractors: K8s images, .node-version, pylock.toml, VirtualBox disk images, openEuler support in RPM extractor
• New secret detectors: 1password, Postgres pgpassfile, crates.io API token
• Package licenses now surfaced in the SPDX output
• Per-file error reporting in scan results

v0.3.5

• New extractors: docker-compose images, nvm packages,
• New secret detectors: Stripe API keys, GCP OAuth2 access tokens, GitHub tokens, Slack tokens, Azure storage account access keys
• Guided remediation: Support for pyproject.toml to relax strategy
• --extractor-override flag which forces specific extractors to run on specific file patterns

... (truncated)

Commits

• f15772b Bump SCALIBR version in preparation for a new release.
• 0afbfa3 Merge pull request #1691 from 0xXA:qemu-plugin
• 389e544 Fix issue with image scanning paths when StoreAbsolutePath is true.
• 3d89e7d Merge pull request #1405 from am0o0:deno-extractor
• 8a56b5c Merge pull request #1786 from 0xXA:simplevalidate-meps-support
• eaf0c6e Merge branch 'main' into simplevalidate-meps-support
• 3f5213e Migrate all remaining detectors to use the global PluginConfig.
• 6c2c598 Use %w for error wrapping in the slacktoken validator.
• 2d45275 Merge pull request #1278 from am0o0:bazel_Maven_Extractor
• e335c95 Merge branch 'main' into simplevalidate-meps-support
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign zoltak-g for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[google-oss-prow]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a GoogleCloudPlatform member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.