• Static_Rocket@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    2 months ago

    You would first need to define malicious code within the context of that repo. To some people, telemetry is malicious.

    • Winfried 🌈@mastodon.nl
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      @Static_Rocket
      @unknowing8343

      Under the GDPR any data processing must be proportional to its goal, the goal must be transparent and justified and the processing must be limited to its goal. Telemetry is perfectly fine if you keep to the rules and malicious if you don’t. So simple are things. And no, this can’t be judged by looking at the repo, it is the deployment that matters. Nonetheless some code is always malicious, some code should be deployed with care. Would be good to scan for those.

    • unknowing8343OP
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      2 months ago

      Yes, of course, the idea would be something like passing the AI a repo link and a prompt like “this repo is supposed to be used for X, tell me if you find anything weird that doesn’t fit that purpose”.