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

[dependabot]

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

Release notes

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

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

v0.3.4

• New secret detectors: DigitalOcean API keys, OpenAI project keys, Tink plaintext keysets, GitLab PAT, HashiCorp Vault+App tokens, GitHub app refresh tokens
  • See the docs for an overview of all currently supported secret types.
• Luarocks software extractor
• Secret detection+validation can now be enabled individually with e.g. --plugins=secrets/gcpsak,secrets/gcpsakvalidate
• Support fetching Maven dependencies from Artifact Registry
• Improvements to semantic version comparison

v0.3.3

• Vulnerability matching on Extracted packages with OSV.dev: Enable in the CLI with --plugins=vulnmatch/osvdev
• Secret extractors with validation: Anthropic API keys, Perplexity API keys, Grok xAI API keys, Docker Hub PAT, private keys,
• Inventory extractors: MacPorts, Winget, asdf package manager, Nimble
• Vuln detectors: Docker Socket Exposure

Thanks to all Patch Reward Program participants for the new plugins!

If you're interested in contributing through the PRP yourself and earning rewards, check out https://bughunters.google.com/about/rules/open-source/6436351477940224/osv-scalibr-patch-rewards-program-rules

v0.3.2

• New plugins: Dockerfile base images, network ports for MacOS, EoL linux distros, transitive requirements.txt dependencies, VEXing for DPKG packages without any binaries, software licenses
• Additional binary types supported by the unknown binary extractor
• CLI flag for scanning a local docker image
• Annotation for NPM packages that are actually installed from NPM repositories
• Support more ecosystems for version comparison

v0.3.1

• Annotation for language packages already found by OS package for RPM, COS, APK
• npm-shrinkwrap.json extraction
• Secret scanning, supporting detection of GCP Service Account keys
• Reachability analysis for Java
• VEX annotation to mark false positive vulnerabilities
• Unknown binary identification
• CLI changes: --plugins= as a unified plugin enablement method
• New Finding Format

v0.3.0

• New CLI flags: --version, --cdx-component-type
• New Plugins: Annotation for language packages already found by OS package for DPKG, transitive requirements.txt extraction

... (truncated)

Commits

• 7d6aea5 Update SCALIBR version in preparation for a new release.
• 154d759 Add per-file error reporting to Scalibrs extraction plugins that might run ov...
• 6ce7196 fix(semantic): handle ecosystems with suffixes.
• 1659c7b Add flag to disable Google Authentication
• 63ca6d5 Merge pull request #1407 from cuixq:pipfile
• f2cdb3d Add package licenses to SPDX output.
• 838ec9d Add support for .tar and .tar.gz traversal.
• cc2a8da Merge pull request #1348 from 0xXA:vdi-plugin
• d55b1c1 Concurrent baseimage enricher queries and adjust ChainID calculation.
• 9d6ff22 Rename annotator from from-npm to npm-source.
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[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 burov for approval. For more information see the Kubernetes Code Review Process.

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

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.

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.