TypeScript good first issues

This issue proposes displaying balance and remaining limit information for third-party company card programs connected via Plaid. The data will be fetched using Plaid's `/accounts/get` API and displayed similarly to the existing Expensify Card page. The refresh strategy involves updating data during transaction scrapes and potentially once daily, with the understanding that real-time updates are not guaranteed and availability varies by issuer.

When using the swipe-back gesture in Safari on an iPhone within the app, the previous screen briefly flickers before transitioning. This visual glitch occurs on any screen of the application and is reproducible in both staging and production environments.

This issue serves as a central hub for advisory findings from Hive agents, particularly at lower ACMM levels where agents analyze code without creating direct issues or PRs. A governor agent periodically posts digest comments summarizing these advisory findings. This issue is intended to be a living document and should not be closed.

This issue requests improvements to the right-side Table of Contents (TOC) on the Meshery documentation site. Currently, the TOC lacks scrollspy highlighting to indicate the active section and does not auto-scroll to keep the active link in view. The desired state is to implement these features for better user navigation and readability.

This issue highlights a conflict between react-native-firebase and react-native-google-mobile-ads on iOS. React-native-firebase is transitioning to Swift Package Manager (SPM) with dynamic linkage, while react-native-google-mobile-ads currently uses static linkage for SPM. This incompatibility prevents developers from using both libraries together in an SPM-based React Native project.

Circuit breakers are being created and reported on in the API, but they are never actually used to wrap outbound calls to services like Soroban, MoonPay, Transak, and CEX. This means the health checks are providing meaningless data, and failing providers are being repeatedly hammered with requests.

This is a beginner-friendly task for Hacktoberfest where contributors can add a new fact about Japan to a JSON file. No coding experience is required, and the contribution can be made directly through the browser in under a minute.

This issue proposes enhancing the CI pipeline for smart contracts by integrating `cargo-audit` and `cargo-deny`. The goal is to automatically check for security advisories and enforce license policies within the Rust dependency tree, preventing potential risks before they are merged.

This issue proposes to improve the theme selection functionality by persisting the user's chosen theme in localStorage and respecting the `prefers-color-scheme` CSS media query for first-time visitors. The goal is to prevent theme flashes on initial load and ensure a consistent user experience across reloads and new visits.

This issue proposes adding a Spanish locale (`es.json`) to the project's internationalization files and implementing a CI check to ensure all locales maintain parity with the base English locale. This will prevent translation drift and improve the robustness of the i18n system.

This issue proposes adding distinct loading, empty, error, and success states to dashboard data panels. The goal is to improve the user experience by providing clear feedback when data is loading, unavailable, or an error occurs, including a retry mechanism for errors and informative messages for empty states. This will replace the current behavior of blank or stale skeleton panels.

This issue proposes adding new read-only functions to a smart contract to suggest potential users to follow. These suggestions will be based on a two-hop connection (friends of friends) and will be paginated, excluding the current user and their existing followees.

This issue proposes adding loading skeleton components to the certificates and insights pages to improve user experience on slow connections. The goal is to prevent blank or jumping layouts by displaying placeholder elements that match the final content's dimensions while data is being fetched. This involves creating new skeleton components and integrating them with the existing data fetching logic.

This issue is a general call for community contributions to improve the localization of the Word-Smith application. Users are encouraged to report incorrect translations, syntax highlighting errors, prose check inaccuracies, or missing languages. The issue also provides guidance on how to submit fixes and contribute new language packs.

This issue proposes to either remove the `frontend/build.ps1` PowerShell script or properly document its purpose and maintenance. The script appears to be unused and unsupported, as there's no mention of it in documentation, CI, or package.json scripts, and other build scripts are in bash. The goal is to ensure clarity and maintainability for Windows build support.

This issue requests a GitHub Action to automate the process of archiving Backstage plugins. The action should be manually triggered, accept a workspace name as input, execute the necessary scripts to archive a plugin, and open a pull request with the changes. It also aims to create an issue to notify relevant parties about the archiving process.

This issue proposes adding MCP (Machine Control Plane) actions to the tech-insights plugin, allowing users to query and interact with tech insights and service maturity data through AI CLIs like Claude and Codex. The implementation would follow a pattern already established in Backstage's catalog and scaffolder plugins, and the author is willing to contribute the PR.

The Copilot backend incorrectly attempts to retrieve an organization installation using an enterprise slug when configured for enterprise metrics. This leads to a 403 error because organization installations cannot access enterprise-level Copilot metrics, and the correct enterprise installation is never consulted.

This issue tracks the migration of numerous community-maintained Backstage plugins from Material UI (MUI) to Backstage UI (BUI). The goal is to update the UI components across these plugins to align with the newer Backstage UI library. Contributors are encouraged to use provided resources and follow a strict one-PR-per-workspace guideline.

The Azure DevOps scaffolder backend module incorrectly throws errors in the task logs when an Azure Pipeline run fails or is canceled. Instead of showing errors, it should accurately report the pipeline's status and any associated errors.

This feature request proposes adding support for specifying a SonarQube branch per entity within the SonarQube plugin for Backstage. Currently, the plugin defaults to the main branch, which often leads to empty or irrelevant data. The proposed solution involves reading an optional `sonarqube.org/branch` annotation to dynamically select the branch for displaying SonarQube metrics.

This issue is a beginner-friendly task for Hacktoberfest, requiring contributors to add a new Japanese grammar point to a JSON file. The contribution involves editing a file directly in the browser, with no coding or setup required, and is estimated to take less than a minute.

This issue requests enhancements to the New Relic plugins in Backstage to support multiple dashboard GUIDs, multiple APM application IDs, and multi-account configurations. Currently, the plugins only allow a single value for each, hindering the representation of complex microservice architectures with diverse monitoring needs across different environments.

This issue requests an update of the `react-router` and `react-router-dom` packages to their latest minor versions within the v6 range. This is a coordinated effort requiring maintainer involvement across multiple workspaces.

This issue proposes to make the PlaylistPage in Backstage's playlist plugin customizable, similar to how the PlaylistIndexPage can already be customized. The goal is to allow users to inject their own components, like security components, without needing to fork the entire page. This would involve exporting relevant components like PlaylistEditDialog and PlaylistHeader.

This issue proposes to deprecate support for React versions 16 and 17 across all frontend plugins in the repository. The goal is to simplify future migration to React 19 by updating `package.json` dependencies to only target React 18 and then resolving any TypeScript errors. Developers are instructed to create a separate Pull Request for each workspace.

This issue reports a bug in the ServiceNow plugin for Backstage where the incidents/tickets table displays the oldest tickets first and includes resolved/closed tickets by default. The user expects the latest tickets to appear on top and resolved/closed tickets to be excluded by default.