awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
christian-bromann avatar

christian-bromann/devtools-backend

0
View on GitHub↗
150 stars·24 forks·JavaScript·Apache-2.0·9 views

Devtools Backend

Standalone implementation of the Chrome DevTools backend to debug arbitrary web environments.

Features

  • Legacy Projects - Standalone backend for debugging arbitrary environments.

Star history

Star history chart for christian-bromann/devtools-backendStar history chart for christian-bromann/devtools-backend

How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Frequently asked questions

What does christian-bromann/devtools-backend do?

Standalone implementation of the Chrome DevTools backend to debug arbitrary web environments.

What are the main features of christian-bromann/devtools-backend?

The main features of christian-bromann/devtools-backend are: Legacy Projects.

What are some open-source alternatives to christian-bromann/devtools-backend?

Open-source alternatives to christian-bromann/devtools-backend include: allada/go-debugger-devtools — Go Debugger using Google Chrome Devtools. auchenberg/devtools-remote — Debug your browser tabs remotely via Chrome DevTools. fate0/pychrome — A Python Package for the Google Chrome Dev Protocol [threading base]. google/ios-webkit-debug-proxy — ios-webkit-debug-proxy is a command-line proxy that bridges Chrome DevTools to Safari Web Inspector on iOS devices,… microsoft/iediagnosticsadapter — IE Diagnostics Adapter is a standalone exe that enables tools to debug and diagnose IE11 using the Chrome remote debug… remotedebug/remotedebug-gateway — A gateway for RemoteDebug (Chrome Remote Debugging) connections, that allows you to connect a client to multiple…

Open-source alternatives to Devtools Backend

Similar open-source projects, ranked by how many features they share with Devtools Backend.
  • allada/go-debugger-devtoolsallada avatar

    allada/go-debugger-devtools

    42View on GitHub↗

    Go Debugger using Google Chrome Devtools

    Go
    View on GitHub↗42
  • auchenberg/devtools-remoteauchenberg avatar

    auchenberg/devtools-remote

    701View on GitHub↗

    Debug your browser tabs remotely via Chrome DevTools

    CSS
    View on GitHub↗701
  • fate0/pychromefate0 avatar

    fate0/pychrome

    646View on GitHub↗

    A Python Package for the Google Chrome Dev Protocol threading base

    Python
    View on GitHub↗646
  • google/ios-webkit-debug-proxygoogle avatar

    google/ios-webkit-debug-proxy

    6,174View on GitHub↗

    ios-webkit-debug-proxy is a command-line proxy that bridges Chrome DevTools to Safari Web Inspector on iOS devices, enabling remote debugging of web content over USB. It translates WebKit remote debugging protocol messages into Chrome DevTools Protocol over persistent WebSocket connections, allowing developers to use Chrome DevTools, Safari Web Inspector, or Firefox DevTools to inspect and debug web content in MobileSafari and UIWebViews on real and simulated iOS devices. The proxy discovers and communicates with iOS devices over USB using the libimobiledevice library without requiring iTunes

    C
    View on GitHub↗6,174
See all 7 alternatives to Devtools Backend→