Skip to content

Missing attribution to mobile-use and its contributors #40

Closed

Description

@lucmahoux

Summary

We’re the team behind mobile-use. Artemis includes code from our project, but we couldn’t find an acknowledgement of Minitap, mobile-use, or its contributors.

We welcome reuse of our open-source work and are requesting that its origins and authors be credited.

Evidence

The initial pyproject.toml contains mobile-use’s version number, 3.6.3, and three original authors: Pierre-Louis Favreau, Jean-Pierre Lo, and Nicolas Dehandschoewercker, under a Google LLC copyright header.

In the replacement commit, those names are replaced with another author. The other 228 files are unchanged.

Shared code includes the ADB tunnel implementation, planner helpers, app-lock utilities, agent prompts, and SDK examples. Some retain mobile-use-specific references, including “Mobile use context” docstrings and the reference to replacing the lim CLI.

Requested resolution

  • Add a README acknowledgement identifying mobile-use by Minitap as a source of the reused code, with a link to the upstream repository.
  • Restore the relevant upstream copyright and attribution notices wherever mobile-use code is incorporated.
  • Credit the original authors and community contributors whose work is included.

Thank you.

Activity

  1. mininic0 commented on Sep 11, 2026

    @mininic0

    On behalf of our Engineering team who spent countless hours working towards this code and reaching 100% success rate, not crediting and claiming these results is a disgrace to the open-source community and to Google's ethos.

  2. MysteryPancake commented on Sep 12, 2026

    @MysteryPancake

    It would be a good idea to report this project to Google as intellectual property copyright infringement:
    https://support.google.com/legal/troubleshooter/1114905

    Google is probably not aware the authors have stolen this code.

  3. MysteryPancake commented on Sep 12, 2026

    @MysteryPancake

    It looks like they recently added a copyright notice to the very bottom of the readme:
    371aa6d

    I don't think this is sufficient copyright notice given how much of this repository is stolen.

  4. ydixken commented on Sep 12, 2026

    @ydixken

    I'll bet it only happened because the instructions the copiers (can't really call them "authors") gave their agent just weren't clear enough!!1

    /s

  5. Sivasankaramalan commented on Sep 12, 2026

    @Sivasankaramalan

    At last there is an acknowledgement from Artemis!!!

    Image
  6. outloudvi commented on Sep 13, 2026

    @outloudvi

    Google tried to make up with 371aa6d but that's not complete. My agent took as much as 81 seconds to find these additional files that are also much similar with files in mobile-use and may also need the same type of attribution:

    artemis/sdk/examples/simple_photo_organizer.py
    artemis/sdk/examples/smart_notification_assistant.py
    artemis/sdk/examples/video_transcription_example.py
    artemis/sdk/types/exceptions.py
    artemis/tools/types.py
    artemis/utils/cli_selection.py
    artemis/utils/conversations.py
    artemis/utils/decorators.py
    artemis/utils/recorder.py
    artemis/utils/requests_utils.py
    artemis/utils/shell_utils.py
    artemis/utils/ui_hierarchy.py
    tests/unit/tools/test_utils.py
    

    I'm amazed by Google who forked a product, added enhancements, got a lower score on AndroidWorld (99.1% v. 100%?), and removed support for cloud devices like BrowserStack.

  7. acockrell commented on Sep 13, 2026

    @acockrell

    I have submitted a PR to correct this oversight.

  8. somew1nd commented on Sep 15, 2026

    @somew1nd
    Collaborator

    The Artemis repository has been updated (commit 371aa6d) to include project-level attribution to Minitap, Inc. in the README files and restore upstream copyright headers across relevant files under Apache 2.0.

    Closing this issue.

  9. locked as resolved and limited conversation to collaborators on Sep 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions