Find meaningful ways to contribute

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.

The documentation in CLAUDE.md for pre-PR gates is incomplete, omitting four essential checks that `just qc` performs. This omission led to a bug where a snippet was truncated mid-word, which was only caught by one of the missing gates. The suggested fix is to update the documentation to include all relevant gates or to dynamically list the output of `just qc`.

This issue is a "good first issue" that invites contributors to add a new Japanese idiom, "腹が立つ" (Hara ga tatsu), to a JSON file. The contribution requires no coding and can be completed directly in the browser within a minute by following simple steps like forking the repository and editing the JSON file.

The current README quick start guide fails for new users after `pip install pysad` because the necessary dataset files are not included with the package. The proposed solution is to modify the `Data` class to download datasets on demand from a remote source into a cache directory, making the quick start functional out-of-the-box.

The vulnerability page currently displays an excessive number of affected range events without any mechanism for truncation or collapsing. This leads to a poor user experience, especially when a vulnerability has many such events, as seen in the provided examples. The goal is to implement a UI solution to manage the display of these events.

The current C++ testing framework, inherited from Haiku, is considered of low quality and needs significant rework. The proposed solution is to rewrite a substantial portion of the framework from scratch to ensure higher quality tests, even if it means fewer of them.

This issue identifies several inaccuracies and omissions in the project's documentation, specifically in the README, CONTRIBUTING, and local setup guides. The documentation misrepresents the scope of `pnpm build` and `pnpm test` commands, fails to mention the `@trusttrove/sdk-react` package and CLI, and shows outdated or incorrect sample test outputs. It also lacks clarity on Go testing prerequisites and a repository layout overview.

This issue is a call for community testing of Twikoo's 2.0 cloud function deployments across various platforms. It details the current testing status for each platform and provides an in-depth analysis and fix for the EdgeOne Makers deployment, which was previously broken due to mismatched contracts and data file retrieval issues. The fix involves adapting the entry point, inlining data, porting SMTP functionality, and optimizing the deployment package.

This issue requires a native Brazilian Portuguese speaker to rewrite a single line in the `README_pt.md` file. The line, which describes Apache Kafka, was added with AI assistance and needs to sound natural and human-written. The task involves editing a specific line in the README, ensuring technical terms remain unchanged, and submitting a pull request.

The user wants to conditionally use a specific service account or the default one specified by GOOGLE_APPLICATION_CREDENTIALS within Kestra. They found that setting `serviceAccount: null` works but a templated approach to dynamically select a service account fails with a JSON input error.

When cancelling an MPP query, if a worker is stuck in a slow filter that doesn't check for interrupts, the entire backend becomes unresponsive. This is because the worker holds interrupts, preventing the leader from properly aborting the transaction, leading to a cluster reset if `kill -9` is the only solution.

The desktop application's embedded browser renders third-party login pages, violating RFC 8252 and causing passkey sign-in to hang indefinitely. This occurs because Electron lacks the necessary authenticator UI and the WebAuthn `get()` request never settles or times out.

This issue addresses several minor bugs and inconsistencies within the application's authentication and authorization modules. Key fixes include correcting cache TTL units to milliseconds, ensuring the correct DTO is used for the one-time password sign-in endpoint, and resolving a typo in the `@Injectable()` decorator. These are presented as independent fixes that can be addressed in separate pull requests.

The project's Makefile and shell scripts incorrectly call `docker-compose` which is deprecated and often not installed on modern Docker setups. Instead, they should use the `docker compose` command, which is part of the Docker Compose v2 plugin. This change will resolve build failures for users who only have the v2 plugin installed.

This issue proposes refactoring the application to replace hard-coded configuration settings with environment variables. This change will improve flexibility, allowing the app to be run outside of Docker Compose and customized without code modifications. Specific settings to be externalized include Redis connection details, OTLP exporter configuration, CORS origins, frontend URLs for emails, and the email sender name.

This issue addresses the lack of unit tests in the project, causing `pnpm test` to fail. The goal is to add unit tests for use cases and services, starting with authentication and billing modules, by mocking dependencies. These tests will be integrated into the CI pipeline.

This issue proposes the implementation of a Continuous Integration (CI) pipeline for GitHub pull requests. The CI workflow should automate the build, linting, and testing processes, including end-to-end tests with database and cache services, to ensure code quality before merging.

The Prometheus configuration in the project is attempting to scrape metrics from a development-specific container name (`otel-collector-dev:8889`), which is causing failures in test and production environments. The suggested fix is to use the generic compose service name (`otel-collector:8889`) for Prometheus scraping and optionally route traces through the OpenTelemetry Collector.

The dev container configuration incorrectly references a non-existent `docker-compose.yml` file. This prevents the project from being opened in a dev container and also causes issues with mounting the project directory, hiding essential files like `node_modules` and the Prisma Client. The suggested fix involves correcting the path to the compose file and adjusting the volume mounts.

This issue proposes adding a `.gitattributes` file to the repository to enforce consistent LF line endings across all files. This will prevent issues with shell scripts, code formatters like Prettier and ESLint, and Docker image builds, which are currently broken by CRLF line endings on Windows.

The project's linting script fails because ESLint 9 defaults to using flat configuration files, while the project currently uses the legacy `.eslintrc.js` format. To resolve this, the project needs to migrate to the new flat configuration format and fix existing linting errors.

This is an epic issue to complete the billing and payment flow, which is currently incomplete and broken. It involves several sub-tasks like saving purchases, handling webhook events, managing subscriptions, sending confirmation emails, and implementing user-facing features like listing purchases and subscriptions. The goal is to create a robust and fully functional billing system integrated with Stripe.

The maintainer of YT Zero is stepping down due to legal uncertainties regarding software and integrations. They plan to release one final version in September 2026, addressing existing issues and improving the tvOS app. The project is open for new maintainers, with the possibility of a future revival using official YouTube APIs.

This issue details three bugs in the v6 branch related to GitHub mentions. First, the 'ioscan' mention is incorrectly audited as 'declined' but still processed, leading to double auditing. Second, the mention detection logic lacks a left-hand boundary check, causing false positives with email addresses and URLs. Third, mention configuration is only loaded at boot and not updated on reloads, meaning changes to mention settings require a restart.

This issue aims to create a new "Framework integrations" section in the documentation to guide newcomers. It will link to relevant discussions, code snippets, and external resources, providing a clear onboarding path for users interested in integrating the project with different frameworks. The goal is to make this a "good first issue" for new contributors.

The `transform_partial` and `fit_transform_partial` methods in PYODScoreEnsembler are incorrectly returning a NumPy array of shape (1,) instead of a single float as documented. This prevents seamless integration with downstream components like calibrators and metric calculations. The fix involves ensuring these methods return a float representation of the combined score.

The score ensemblers in pysad are failing when provided with a Python list of scores, as they expect a NumPy array. This is because the `transform_partial` method directly attempts to reshape the input, leading to an AttributeError. The fix involves converting the input list to a NumPy array before reshaping and adding a test to verify this behavior.

The ZScorePostprocessor and RunningZScorePostprocessor currently return NaN for scores with zero variance, such as the first score or a window of identical scores. This NaN value causes ensembler components to crash because they do not accept NaN inputs. The expected behavior is to return a z-score of 0.0 in these zero-variance scenarios.