this post was submitted on 31 Aug 2024
19 points (74.4% liked)
Open Source
31044 readers
890 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You would first need to define malicious code within the context of that repo. To some people, telemetry is malicious.
@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.
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".