Find meaningful ways to contribute

A test in the `PerformanceCounterCategory_GetCounters` test suite is failing on an ARM64 Windows build. The error indicates that a required performance counter category, 'PerformanceCounterCategory_GetCounters_Category', does not exist, suggesting a potential race condition or setup issue during test execution.

This issue proposes adding functionality to convert images into a Meshery Design format. The current behavior is not described, but the desired behavior is to enable this image-to-design conversion. The implementation details, acceptance tests, and mockups are not provided, but the issue is tagged for enhancement and involves JavaScript, CSS, and HTML.

This issue proposes the creation of a validating webhook for the Burrito project. The webhook will be responsible for validating resources before they are applied, specifically focusing on the `remediationStrategy` enum and complex interactions between various options.

This issue requests the implementation of a new Git provider for Bitbucket. It specifically mentions building upon the new structural changes introduced in a recent pull request, indicating a need to integrate with an existing framework.

This issue proposes adding a new configuration setting to the Burrito tool. This setting would prevent Burrito from executing 'apply' operations if the 'plan' output indicates that any resources are scheduled for destruction. The goal is to enhance safety and facilitate adoption on critical Terraform code by preventing accidental resource deletion.

When a component's VDOM update is deferred due to an in-flight ancestor or descendant update, it incorrectly leaves its `needsVdomUpdate` flag as false. This prevents subsequent sibling updates from merging into the pending ancestor update, leading to disjoint VDOM update cycles.

The mutation advisory workflow times out after 20 minutes on large pull requests, preventing the generation of a mutation report. This results in either no comment or a stale comment on the PR, leaving users unaware of the mutation status. The proposed solution is to implement a per-package timeout within the mutation report script to ensure a comment is always generated, even if partial.

The `flisk demo` command, which is the first command new users are encouraged to run, is not discoverable through `flisk --help` or `flisk demo --help`. This issue proposes adding `demo` to the root help, providing a dedicated help message for `flisk demo --help`, and ensuring these help messages are tested to maintain discoverability.

This issue addresses inaccuracies in the `adding-alerts.md` documentation. It requires correcting the explanation of the alert integration model from pull to push via webhooks and updating the alert states from 'Active'/'Dismissed' to 'firing'/'resolved', including the 'silenced' and 'unread' flags.

The automated process for generating a Software Bill of Materials (SBOM) for stable releases of finpilot is failing. The SBOM generation step is being cancelled prematurely on GitHub-hosted runners, resulting in releases being published without the required package list. This is likely due to resource constraints on the runner, such as disk space or memory, during the SBOM generation process.

The MatterBridge-hass plugin is failing to expose multiple entities with identical names (e.g., 'Thermostat') to Apple Home. This appears to be a naming conflict, as renaming the entities to be unique resolves the issue. The user is seeking a solution to allow duplicate entity names.

This issue proposes adding support for SHA-512-crypt ($6$) hashing to the Brutecraber tool. Currently, the tool only supports raw SHA-512, which is insufficient for cracking common Linux shadow file hashes. The implementation should handle the standard $6$ format, including optional round parameters, and ensure proper auto-detection and error handling.

The SG-003 rule in SkillGuard incorrectly flags common phrases like "escalate the ticket" and "admin access" as critical security risks. This is due to an overly broad regular expression that needs to be refined to distinguish between genuine privilege escalation attempts and benign usage of these terms. The goal is to reduce false positives without compromising the detection of actual security threats.

This issue requests an enhancement to SARIF output to include files that could not be read during a directory scan. Currently, these unreadable files are omitted from SARIF, preventing GitHub code scanning from indicating that files were skipped. The proposed solution involves adding `toolExecutionNotifications` entries for each unreadable file with an error level, ensuring the output remains valid SARIF.

This issue requires adding a new test to `tests/test_skillshield.py` to verify the existing 50-snippet cap on line-number lookups in `src/skillshield/scanner.py`. The test should simulate a scenario with more than 50 snippets and confirm that only the first 50 have their line numbers reported, preventing performance degradation.

This issue requests the implementation of support for the NO_COLOR environment variable and a `--no-color` command-line option. This will allow users to disable colored output in the text report, improving accessibility for those who have difficulty reading it, while maintaining the current behavior of disabling color when output is not to a terminal.

This issue proposes adding a `--format json` option to the `skillshield rules` command. This would allow tools and documentation generators to easily consume rule data in a structured JSON format, improving integration and automation capabilities. The existing text output would remain the default.

This issue requests updating the project's Continuous Integration (CI) to include testing on Python 3.13 and 3.14, as these versions are now released and in use by many users. The necessary changes involve updating the CI workflow files and the project's metadata to reflect support for these new Python versions.

This issue requests the replacement of a manually updated test count badge in the README with an automatically updating GitHub Actions CI status badge. The current badge is outdated and will continue to be so. Additionally, any other hardcoded test counts in the documentation should be removed or updated.

This issue proposes a new security rule (SG-016) to detect when TLS certificate checks are disabled for package installations and downloads. This is a security risk as it allows for man-in-the-middle attacks. The rule should flag common commands and configurations that disable these checks, while ensuring safe near-misses are not flagged.

This issue describes a detection gap where invisible Unicode variation selectors can be used to hide data within seemingly normal characters, like emojis. The goal is to update the SG-008 detection rule to flag runs of more than two variation selectors, while excluding normal emoji usage, and to display the hidden data in the findings.

This issue proposes enhancing detection rules to identify malicious code that decodes or decompresses data before executing it. The current detection is SAFE, but the goal is to extend existing rules (SG-006) to flag patterns like `exec(base64.b64decode(...))` in Python and `eval(atob(...))` in JavaScript. The focus is on the combination of execution and decoding, not just decoding for inspection.

This issue proposes adding a new detection rule to identify the use of `LD_PRELOAD` (Linux) and `DYLD_INSERT_LIBRARIES` (macOS). These environment variables allow a library to be loaded into other programs, which can be used for both malicious and legitimate purposes. The rule should flag instances where these variables are set, especially when pointing to temporary or download directories, to prompt reviewer investigation.

This issue proposes a new security rule to detect malicious Git configurations that can execute arbitrary code or steal credentials. The rule should flag specific `git config` settings like `core.hooksPath`, `core.sshCommand`, `core.pager`, `core.editor`, `core.fsmonitor`, and `credential.helper` when set globally or system-wide. It also requires ensuring that legitimate Git configurations and documentation are not flagged.

This issue requests adding a "Severity" section to the documentation pages for Grafana, GCP, Uptime Kuma, and Zabbix integrations. Currently, only the Datadog integration page explains how to set alert severity, leading to users receiving all alerts as 'warning' by default. The proposed solution involves updating the respective Markdown files in the documentation repository to reflect how severity can be configured for each integration.

This issue requests updates to the Grafana integration documentation. Specifically, it asks to change the terminology from 'archived' to 'resolved' for cleared alerts and to add a section explaining how alert names, summaries, and links are constructed from Grafana data within OpsiMate.

This issue highlights a security vulnerability where stored credentials are not truly masked when looked up, potentially leading to them being exposed in session transcripts. The proposed fix involves modifying the credential lookup mechanism to inject credentials directly into the child process environment and mask their output, while also adding advisories for commands that might inadvertently expose credentials.

This issue proposes a new configuration option for rustfmt to give users more granular control over how match arm bodies are block-wrapped. The goal is to support several distinct wrapping behaviors, ranging from the current default to always wrapping, preserving existing wrapping, and wrapping based on line width constraints.

The `flisk down --prune-cache` command accepts and advertises duration units like '7d' which Docker's `builder prune` command does not support, leading to a failure after the stack has already been stopped. The issue stems from a mismatch between the validator's accepted units and Docker's actual parsing capabilities.

This issue describes a bug where failures in the `patch-file` tool are not logged, making it impossible for operators to diagnose why a patch operation failed. The current implementation only logs successful patches, leaving no trace of errors like `NOT_FOUND`, `AMBIGUOUS`, or `NO_CHANGE`. The proposed fix is to log all outcomes, including failures, with relevant details to improve debugging.