[dependabot]

Bumps the github-actions group with 3 updates: OWASP/cve-lite-cli, github/codeql-action/upload-sarif and zizmorcore/zizmor-action.

Updates OWASP/cve-lite-cli from 1.40.0 to 1.41.0

Release notes

Sourced from OWASP/cve-lite-cli's releases.

v1.41.0 - Custom OSV endpoint fix, npm alias scanning and SBOM dependency scope

Upgrade note. This release contains a security fix for custom --osv-url endpoints (GHSA-mrvp-qgq4-c66g); upgrade if you point the scanner at your own OSV mirror. The minimum supported Node.js version is now 22, and CI tests Node 22 alongside Node 24. SARIF locations from a subdirectory scan now carry the folder path, so if you add that prefix yourself, drop that step or the path doubles. Projects that ship an npm-shrinkwrap.json now get fix commands and complete SBOM dependency links where they previously got neither.

Security

• A custom --osv-url is now checked at connection time, not only at startup. The address was validated once, and the request then looked the name up again, so a hostname whose DNS answer changed in between could pass the check with a public address and then connect to a private one. Every connection to a custom OSV host now resolves the name itself, refuses it if any returned address is private or reserved unless --allow-private-osv-url is set, and connects only to the addresses it just checked. Official OSV hosts are unchanged.

Added

• --output - writes the JSON, SARIF or SBOM report to standard output for piping into other tools, with banners and messages kept off the stream. Asking for more than one format with --output - is rejected.
• --output accepts a file path as well as a directory, so CI can write to a stable filename. A path that already exists as a file, or ends in a recognised report extension, is written to directly; anything else keeps the directory behaviour.
• --debug produces one diagnostic bundle meant for attaching to an issue: an environment record, a machine-readable event stream and a summary of the project's shape, with home paths, tokens and private registry hosts left out. Package and workspace names are kept, so check them before attaching from a private project. A directory that cannot be written no longer turns a working scan into a crash, and the failure now names the file and the cause.
• The scan JSON carries the verified parent-upgrade chain for a transitive finding: which direct dependency to move, from which version to which, and the safe version that results.
• SBOMs keep the difference between development and production dependencies. SPDX marks dev-only edges as DEV_DEPENDENCY_OF, and CycloneDX components carry scope (optional for dev, required for production).
• First steps of experimental Python support: PyPI versions are read and ordered by PEP 440, and package URLs can be built per ecosystem. No Python lockfile is scanned yet, and Python packages do not appear in SBOMs.

Changed

• The supported Node.js floor moves from 20 to 22, and CI now runs the full suite on Node 22.
• An SPDX SBOM whose dependency links had to be rebuilt from recorded paths now says so, in a terminal warning and a document-level note, since those links may be incomplete.
• The multi-folder section headers take their wording from the same place as the gate classes, so the two can no longer drift apart.

Fixed

• A package installed under an npm alias is scanned as the package it really is. An alias such as http-client for axios@0.21.1 used to match no advisories and pass --fail-on high on a vulnerable tree. Fix commands keep the alias spec.
• --only-used and the phantom-dependency checks read .mts and .cts files, so a vulnerable package imported only from them is no longer dropped.
• A partial scan no longer writes a SARIF log that reads as clean. A finding whose advisory details could not be fetched is reported as a warning-level result telling you to re-run, and the run is marked unsuccessful, so Code Scanning does not close open alerts.
• npm-shrinkwrap.json is treated as the npm lockfile it is everywhere: fix commands, transitive remediation and SBOM dependency links. When a project holds both npm lockfiles, at the root or in a nested folder, the shrinkwrap is read, as npm does.
• The override-hygiene rules read the same root lockfile the scan reads, so findings and override targets no longer describe two different trees.
• A within-range update is offered only when every parent holding the installed copy accepts the target version, and a parent upgrade is no longer offered when another dependency would keep the vulnerable copy installed. In both cases the command used to run and change nothing.
• The transitive remediation modules evaluate version ranges with one shared implementation, so a range such as 1.2.x no longer makes every comparison silently false.
• --fix no longer runs a second command hidden in a workspace path, since commands are now built as argument lists.
• cve-lite advisories sync keeps the existing advisory database until its replacement is fully downloaded and checked, so a failed refresh no longer leaves offline scans with nothing to read.
• SARIF from a subdirectory scan points at that subdirectory's lockfile instead of a same-named file at the repository root.
• An unrecognised --fail-on value is rejected instead of quietly falling back to critical. moderate, npm audit's name for medium, used to give a passing build.
• A flag that takes a value no longer swallows the next flag when its value is left out. --offline-db, --cache-dir, --osv-url, --audit-log, --rule, --min-severity, --search-depth, --batch-size, --ca-cert and config set ca-cert all stop with <flag> requires a <noun> argument.
• --sbom= with an empty value stops with the list of supported SBOM formats instead of being accepted as an unknown format.
• An invalid --batch-size is rejected instead of running out of memory.
• A 0.0.x patch upgrade is marked as breaking, since a caret range there pins the patch: ^0.0.3 accepts only 0.0.3.
• Shared JSON artefacts no longer record the absolute path of the machine that produced them.
• A flag-conflict error no longer prints an unrelated corporate SSL proxy hint.
• Queued OSV advisory batches no longer start after one of them has failed.
• The Release workflow no longer interpolates the release tag into a shell command.
• Editor swap, undo and autosave files are ignored by git.

Tests

• The SPDX tests validate generated documents against the official SPDX 2.3 JSON schema.
• CI type-checks test files: a pull request's new and changed tests must be clean, and no other file may gain a type error.
• New direct coverage for the finding helpers, the phantom-dependency helpers, the typo-correction helpers, the registry remediation route and the usage-scan file cap.

... (truncated)

Changelog

Sourced from OWASP/cve-lite-cli's changelog.

Changelog

All notable changes to CVE Lite CLI will be documented in this file.

[Unreleased]

[1.41.4] - 2026-11-13

Upgrade note. This release contains one security fix and nothing else.

Security

• A package name that looks like a command-line option, such as an npm alias named --registry=https://... or --ignore-scripts=false, is no longer put into a printed fix command or run by --fix. Since 1.41.0 such an alias is scanned under the real package it points at, so it could produce a finding whose fix command the package manager read as a setting, for example pointing npm install at another registry. The finding is now listed as skipped with the reason (GHSA-5583-5qpr-q69x). Reported and fixed by @​S3DFX-CYBER.

[1.41.3] - 2026-11-13

Upgrade note. This release contains one security fix and nothing else.

Security

• A copyable command is no longer printed for a package, workspace or folder name that would still run something if pasted into Windows cmd.exe or PowerShell. The quoting added in 1.41.1 and 1.41.2 only protects POSIX shells such as bash, zsh and sh, so a name containing &, |, <, >, ^, %, !, a quote, a backtick or a control character now gets no command in the fix plan, the npm ls hints, the PD001 and PD002 install hints or the override --fix command; the finding is listed as skipped with the reason, and the fix count drops to match. Ordinary names, including folder names with spaces, are unchanged (GHSA-x5r8-cxwg-fhm4).

[1.41.2] - 2026-11-12

Upgrade note. This release contains two security fixes and nothing else.

Security

• Package names read from a lockfile or package.json are now quoted in every copyable command the scanner prints: the npm ls inspection hints, the install commands for phantom dependencies (PD001 and PD002), and chain-resolution and fix-plan commands, in the terminal, the HTML report and JSON. A repository could name a package with shell syntax so that pasting the suggested command ran something else. The quoting is POSIX shell quoting, which covers shells such as bash, zsh and sh; 1.41.3 withholds the command for names that Windows cmd.exe or PowerShell would still act on (GHSA-9v96-p5c5-2frh). Reported and fixed by @​Nachiket-Roy.
• Packages installed through an npm alias in overrides or peerDependencies are now scanned under their real registry name, including nested, versioned and $ references in overrides and lockfile v2 and v3. They were looked up under the alias, so a vulnerable package reported clean and passed --fail-on. A peer alias is only applied when the installed package really is the aliased one, so a peer that npm did not install cannot relabel another package (GHSA-6vp2-w78m-6gf7). Reported and fixed by @​Nachiket-Roy.

[1.41.1] - 2026-11-10

Upgrade note. This release contains three security fixes and nothing else. If your project's own .npmrc or .yarnrc.yml points at an internal or plain-HTTP registry, metadata lookups to it are now refused. To use it for a scan, set NPM_CONFIG_REGISTRY, or remove the registry from the project's config and set it in your user-level config (~/.npmrc or ~/.yarnrc.yml); on Windows, use the user-level config. See the corporate proxy docs.

Security

• Yarn classic (v1) projects that install a package through an npm alias, such as "util-lib": "npm:lodash@4.17.20", are now scanned under the real package name. The alias was looked up under a name that does not exist, so a vulnerable package reported "No known vulnerabilities found" and passed --fail-on. Fix commands keep the alias, for example yarn add util-lib@npm:lodash@4.18.1 (GHSA-c8j3-f9pr-q5jg). Reported and fixed by @​alex-powell.
• Folder names are now quoted in the copyable cd fix commands printed in the terminal and the HTML report, including override fix commands. A repository folder named with shell syntax could otherwise run a command when the suggestion was pasted (GHSA-5r8q-h59x-3m7v). Reported and fixed by @​vianmangal.
• Registry addresses taken from the scanned repository's .npmrc or .yarnrc.yml must now use HTTPS and resolve to public addresses, checked for every connection, and redirects are refused, both for remediation lookups and for the override audit. This also applies when npm or npx passes the repository's registry on to the scanner as npm_config_registry. A repository could otherwise make the scanner send requests to internal addresses. Internal registries can still be used through user-level configuration or NPM_CONFIG_REGISTRY (GHSA-2v68-94gw-jr4g). Reported and fixed by @​vianmangal, and found independently by @​Nachiket-Roy.

[1.41.0] - 2026-11-05

Upgrade note. This release contains a security fix for custom --osv-url endpoints (GHSA-mrvp-qgq4-c66g); upgrade if you point the scanner at your own OSV mirror. The minimum supported Node.js version is now 22, and CI tests Node 22 alongside Node 24. SARIF locations from a subdirectory scan now carry the folder path, so if you add that prefix yourself, drop that step or the path doubles. Projects that ship an npm-shrinkwrap.json now get fix commands and complete SBOM dependency links where they previously got neither.

Security

• A custom --osv-url is now checked at connection time, not only at startup. The address was validated once, and the request then looked the name up again, so a hostname whose DNS answer changed in between could pass the check with a public address and then connect to a private one. Every connection to a custom OSV host now resolves the name itself, refuses it if any returned address is private or reserved unless --allow-private-osv-url is set, and connects only to the addresses it just checked. Official OSV hosts are unchanged.

Added

... (truncated)

Commits

• 35c4739 release: v1.41.0 (#1533)
• 17f51a1 Merge commit from fork
• 8f98a2e fix(cli): reject empty sbom format value (#1505)
• 105f72a feat(versions): order PyPI versions with PEP 440 (#1397)
• 67de509 ci: fail the test type-check when a source change breaks an unchanged test (#...
• 7b8bb6b feat(cyclonedx): emit component.scope for dev and prod dependencies (#1488)
• 69736cc fix: preserve last good advisory DB on failed refresh (#1483)
• 509e475 docs(website): clarify local scan privacy claim on homepage (#1496) (#1498)
• 34c04d0 feat(spdx): use DEV_DEPENDENCY_OF relationship for dev dependencies (#1487)
• 3cb5842 fix(overrides): read the lockfile the scan selected (#1506)
• Additional commits viewable in compare view

Updates github/codeql-action/upload-sarif from 4.39.1 to 4.39.3

Release notes

Sourced from github/codeql-action/upload-sarif's releases.

v4.39.3

• Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

v4.39.2

• Update default CodeQL bundle version to 2.27.4. #4284
• Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
• Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

Changelog

Sourced from github/codeql-action/upload-sarif's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.39.3 - 04 Nov 2026

• Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

4.39.2 - 03 Nov 2026

• Update default CodeQL bundle version to 2.27.4. #4284
• Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
• Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

4.39.1 - 21 Oct 2026

• Update default CodeQL bundle version to 2.27.3. #4256

4.39.0 - 15 Oct 2026

• Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #4205
• The codeql-action/analyze step now validates that a correct argument for the checkout_path input has been provided. The checkout_path input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by codeql-action/init, then the CodeQL Action now produces a warning. #4148
• Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. #4206
• The codeql-action/start-proxy step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as codeql-action/init. This primarily benefits customers who are using GitHub instances other than github.com where the codeql-action/start-proxy step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #4198

4.38.3 - 08 Oct 2026

• Upcoming breaking change: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4188
• Update default CodeQL bundle version to 2.27.2. #4203
• Fixed a bug where the decision of whether to use a per-language bundle did not account for custom configurations that reference queries outside of compiled CodeQL packs. This issue was caught during internal testing and did not affect any customer repositories. We will resume the roll out of per-language bundles in the coming weeks. #4184

4.38.2 - 24 Sept 2026

• Update default CodeQL bundle version to 2.27.1. #4160

4.38.1 - 18 Sept 2026

• The CodeQL Action now has experimental support for CodeQL releases for which per-language bundles are available. Per-language bundles support analysis for a single language and are therefore smaller than the combined bundles that allow analysis for all supported languages. As a result, per-language bundles take up less space on disk and are faster to download. We expect to roll this change out to everyone in the coming weeks. #4146

4.38.0 - 09 Sept 2026

• On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. #4124
• The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native linux-arm64 CodeQL bundle when available. #4072
• Update default CodeQL bundle version to 2.27.0. #4129

... (truncated)

Commits

• 33d7b85 Merge pull request #4299 from github/update-v4.39.3-064910ba2
• 24393f8 Update changelog for v4.39.3
• 064910b Merge pull request #4297 from github/mbg/update-glob
• f532ac5 Update glob to 14.0.3
• 8cd4dfa Merge pull request #4280 from github/mbg/ci/validate-yaml
• cea289b Return different exit code when a language is not recognised
• 7287bb3 Remove exclude entry that's no longer needed
• 8eb7cdf Use normal .editorconfig pattern
• 160e547 Merge remote-tracking branch 'origin/main' into mbg/ci/validate-yaml
• 913e1bb Merge pull request #4283 from github/sam-robson/decode-diff-informed-sarif-uris
• Additional commits viewable in compare view

Updates zizmorcore/zizmor-action from 0.8.0 to 0.8.1

Release notes

Sourced from zizmorcore/zizmor-action's releases.

v0.8.1

Sponsorship is appreciated!

zizmor 1.32 is now the default version used by this action.

Full release notes: zizmorcore/zizmor-action#1320

Full Changelog: zizmorcore/zizmor-action@v0.8.0...v0.8.1

Commits

• 45d7276 Sync zizmor versions (#191)
• ff38741 chore(deps): bump the github-actions group across 1 directory with 2 updates ...
• 4a9eca4 README: another troubleshooting section (#186)
• 83a0416 Bump pins (#185)
• See full diff 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: open-circle/formisch
• Branch: main
• File: .coderabbit.yaml
• Commit: b294051
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 4c635391-5c80-40ff-bb81-57d700cc2bf4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn