Repository navigation
chore(deps, cpp): update github.vscode-pull-request-github in devcontainer.json - #144
Open
embedded-releaser-app[bot] wants to merge 1 commit into
Conversation
embedded-releaser-app
Bot
added
dependencies
Contributor
✅
|
| Descriptor | Linter | Files | Fixed | Errors | Max errors | Warnings | Elapsed time |
|---|---|---|---|---|---|---|---|
| ✅ ACTION | actionlint | 25 | 0 | 0 | 0.5s | ||
| zizmor | 25 | 0 | 0 | 1 | 4.65s | ||
| ✅ DOCKERFILE | hadolint | 3 | 0 | 0 | 0.49s | ||
| ✅ JSON | npm-package-json-lint | yes | no | no | 0.51s | ||
| ✅ JSON | prettier | 22 | 3 | 0 | 0 | 0.79s | |
| ✅ JSON | v8r | 22 | 0 | 0 | 9.46s | ||
| ✅ MARKDOWN | markdownlint | 12 | 0 | 0 | 0 | 1.21s | |
| ✅ MARKDOWN | markdown-table-formatter | 12 | 0 | 0 | 0 | 0.57s | |
| ✅ REPOSITORY | betterleaks | yes | no | no | 1.34s | ||
| ✅ REPOSITORY | checkov | yes | no | no | 22.26s | ||
| ✅ REPOSITORY | git_diff | yes | no | no | 0.02s | ||
| ✅ REPOSITORY | grype | yes | no | no | 107.58s | ||
| osv-scanner | yes | 1 | 1 | 1.64s | |||
| ✅ REPOSITORY | secretlint | yes | no | no | 1.59s | ||
| ✅ REPOSITORY | syft | yes | no | no | 4.7s | ||
| ✅ REPOSITORY | trivy | yes | no | no | 13.82s | ||
| ✅ REPOSITORY | trivy-sbom | yes | no | no | 0.6s | ||
| ✅ REPOSITORY | trufflehog | yes | no | no | 6.37s | ||
| lychee | 88 | 1 | 0 | 11.46s | |||
| ✅ YAML | prettier | 33 | 0 | 0 | 0 | 1.25s | |
| ✅ YAML | v8r | 33 | 0 | 0 | 10.3s | ||
| ✅ YAML | yamllint | 33 | 0 | 0 | 1.34s |
Detailed Issues
⚠️ SPELL / lychee - 1 error
📝 Summary
---------------------
🔍 Total..........133
🔗 Unique.........112
✅ Successful.....127
⏳ Timeouts.........0
🔀 Redirected......15
👻 Excluded.........0
❓ Unknown..........0
🚫 Errors...........1
⛔ Unsupported......1
Errors in .github/TOOL_VERSION_ISSUE_TEMPLATE.md
[403] https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads (at 30:7) | Rejected status code: 403 Forbidden
Hint: Followed 15 redirects. You might want to consider replacing redirecting URLs with the resolved URLs. Use verbose mode (`-v`/`-vv`) to see redirection details.
Hint: You can configure accepted/rejected response codes with `-a` or `--accept`
⚠️ REPOSITORY / osv-scanner - 1 error
warning: Package 'minimatch@10.2.4' is vulnerable to 'CVE-2026-118764' (also known as 'GHSA-g3hv-75wg-m249').
= CVE-2026-118764: minimatch has potential denial of service via globparts amplification
= minimatch 10.2.6 contains an attacker-controlled pattern amplification in firstPhasePreProcess() when optimizationLevel >= 2.
researcher: Reid Downing (b1nv0id)
files:
- src/index.ts: 690-770
- src/index.ts: 780-796
issue:
input-controlled growth of globParts during first-phase preprocessing, followed by quadratic second-phase processing.
the **/../ transformation clones a globparts entry and appends the clone to the same globparts array:
parts.splice(gs, 1)
const other = parts.slice(0)
other[gs] = '**'
globParts.push(other)
this occurs inside a do...while (didSomething) fixpoint loop, allowing generated entries to be processed again.
the expanded globparts array is subsequently processed by secondPhasePreProcess(), which performs pairwise comparisons:
for (let i = 0; i < globParts.length - 1; i++) {
for (let j = i + 1; j < globParts.length; j++) {
this.partsMatch(...)
}
}
an attacker who can supply a glob pattern can therefore cause additional pattern entries to be generated during preprocessing, followed by quadratic pairwise processing, resulting in excessive cpu and memory consumption.
warning: 1 warnings emitted
⚠️ ACTION / zizmor - 1 warning
INFO zizmor: 🌈 zizmor v1.25.0
WARN audit: zizmor: one or more inputs contains YAML anchors; see https://docs.zizmor.sh/usage/#yaml-anchors for details
INFO audit: zizmor: 🌈 completed .github/workflows/build-push-test.yml
INFO audit: zizmor: 🌈 completed .github/workflows/continuous-integration.yml
INFO audit: zizmor: 🌈 completed .github/workflows/image-cleanup.yml
INFO audit: zizmor: 🌈 completed .github/workflows/issue-cleanup.yml
INFO audit: zizmor: 🌈 completed .github/workflows/issue-creation-tool-versions.yml
INFO audit: zizmor: 🌈 completed .github/workflows/linting-formatting.yml
INFO audit: zizmor: 🌈 completed .github/workflows/ossf-scorecard.yml
INFO audit: zizmor: 🌈 completed .github/workflows/pr-conventional-title.yml
INFO audit: zizmor: 🌈 completed .github/workflows/pr-image-cleanup.yml
INFO audit: zizmor: 🌈 completed .github/workflows/pr-report.yml
INFO audit: zizmor: 🌈 completed .github/workflows/release-build.yml
INFO audit: zizmor: 🌈 completed .github/workflows/release-please.yml
INFO audit: zizmor: 🌈 completed .github/workflows/update-dependencies.yml
INFO audit: zizmor: 🌈 completed .github/workflows/vulnerability-scan.yml
INFO audit: zizmor: 🌈 completed .github/workflows/wc-acceptance-test.yml
INFO audit: zizmor: 🌈 completed .github/workflows/wc-build-push-test.yml
INFO audit: zizmor: 🌈 completed .github/workflows/wc-build-push.yml
INFO audit: zizmor: 🌈 completed .github/workflows/wc-dependency-review.yml
INFO audit: zizmor: 🌈 completed .github/workflows/wc-document-generation.yml
INFO audit: zizmor: 🌈 completed .github/workflows/wc-integration-test-docker.yml
INFO audit: zizmor: 🌈 completed .github/workflows/wc-integration-test-podman.yml
INFO audit: zizmor: 🌈 completed .github/workflows/wc-integration-test.yml
INFO audit: zizmor: 🌈 completed .github/workflows/wc-mirror-image.yml
INFO audit: zizmor: 🌈 completed .github/workflows/wc-publish-templates.yml
INFO audit: zizmor: 🌈 completed .github/workflows/wc-sanitize-image-name.yml
{
"$schema": "https://docs.oasis-open.org/sarif/sarif/v2.1.0/os/schemas/sarif-schema-2.1.0.json",
"runs": [
{
"invocations": [
{
"executionSuccessful": true
}
],
"results": [],
"tool": {
"driver": {
"downloadUri": "https://github.com/zizmorcore/zizmor",
"informationUri": "https://docs.zizmor.sh",
"name": "zizmor",
"rules": [],
"semanticVersion": "1.25.0",
"version": "1.25.0"
}
}
}
],
"version": "2.1.0"
No fixes available to apply.
}
Notices
REPOSITORY_KICS. See Removed linters to find their replacements.
See detailed reports in MegaLinter artifacts
You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:
- oxsecurity/megalinter/flavors/salesforce@v10.1.0 (58 linters)
Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)
- Documentation: Custom Flavors
- Command:
npx mega-linter-runner@10.1.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,ACTION_ZIZMOR,DOCKERFILE_HADOLINT,JSON_V8R,JSON_PRETTIER,JSON_NPM_PACKAGE_JSON_LINT,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_BETTERLEAKS,REPOSITORY_GRYPE,REPOSITORY_OSV_SCANNER,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R
Show us your support by starring ⭐ the repository
Contributor
📦 Container Size AnalysisNote Comparing 📈 Size Comparison Table
|
Contributor
📦 Container Size AnalysisNote Comparing 📈 Size Comparison Table
|
Contributor
📦 Container Size AnalysisNote Comparing 📈 Size Comparison Table
|
Contributor
Test Results 12 files 12 suites 17m 3s ⏱️ Results for commit 95c6073. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Before merging this PR, please conduct a manual test checking basic functionality of the updated plug-ins. There are limited automated tests for the VS Code Extension updates.
Updates
github.vscode-pull-request-githubfrom 0.172.0 to 0.174.0Release notes