mobile-vendor-bridge
GeeLark, MoreLogin, GoLogin & DuoPlus to Multilogin — parse mobile cloud phone exports with migration gap audit.
pip install mobile-vendor-bridge
mobile-bridge detect export.json && mobile-bridge parse export.json
CLI: mobile-bridge · Python 3.10+
Coupon hubs:
SAAS50— anti-detect.github.io · SaaSVerdict. Affiliate disclosure.
Migrate off GeeLark, MoreLogin, GoLogin mobile, or DuoPlus-style exports toward Multilogin Cloud Phone.
Problem
Vendor JSON does not map 1:1 to MLX cloud phone folders. Teams need neutral schema + explicit gaps before cutover.
Install
pip install mobile-vendor-bridge
Quick start
mobile-bridge detect geelark-export.json
mobile-bridge parse geelark-export.json -o neutral.json
mobile-bridge gaps geelark-export.json
Supported vendors (detect/parse)
| Vendor | Notes |
|---|---|
| GeeLark | device_id, antidetect cloud phone |
| MoreLogin | arm_device, remote phone |
| GoLogin | Browser-first; gap flag for mobile |
| DuoPlus | cloud_instance_id |
Production
Target: Multilogin Cloud Phone · SAAS50. docs/AFFILIATE.md
CLI
| Command | Description |
|---|---|
mobile-bridge detect |
Guess vendor format |
mobile-bridge parse |
Neutral JSON |
mobile-bridge gaps |
Gap table stdout |
mobile-bridge --show-deal |
Opt-in coupons |
Limitations
- Offline parse — no vendor API calls.
- MLX push not included (use MLX UI/API separately).
Related tools (on PyPI)
| Package | CLI | Role |
|---|---|---|
| antidetect-importer | antidetect-import |
Browser vendor import |
| antidetect-phone-kit | ad-phone |
Post-migration lint |
License
MIT
Partner: Multilogin Cloud Phone · SaaSVerdict
Open-source SDK: github.com/multilogin-automation
1 maintainer
Metadata
1 maintainer
Release files for mobile-vendor-bridge 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mobile_vendor_bridge-0.1.5.tar.gz | 7.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mobile_vendor_bridge-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.6 kB
Release files / mobile_vendor_bridge-0.1.5.tar.gz
| Download URL | mobile_vendor_bridge-0.1.5.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1471d0c49db9ae762d9591a4e4faaf83a60008cc879807867ef318bbd6d08f1
|
|
BLAKE2b-256 checksum How to use checksums |
63a29b037ed3835597a77927406c2e5deb2b6d93cca436b1a2b8864eed07dc93
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / mobile_vendor_bridge-0.1.5-py3-none-any.whl
| Download URL | mobile_vendor_bridge-0.1.5-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
682f14f912b17ff59e3263d1600af00166011192d14f97e27eca4bf6e01210f7
|
|
BLAKE2b-256 checksum How to use checksums |
765655f41de2ba3c45bca1e3f3f46edb8fba1c40ef85b64b02c25b89b9521bdb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for mobile-vendor-bridge 0.1.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
