需求卡片 #56 · 相关性 中 · 新发现

F-Droid 应用 AI 生成代码的透明度不足

更新于 2026/9/21 13:20:56

问题概述

用户在 F-Droid 生态中对应用代码是否由 AI 生成缺乏清晰标识,导致对安全性和可信度的担忧,且缺乏有效的检测手段。

痛点标签

待验证问题

证据

原话 · @匿名 · 来源 #comment_4
I have been working on a sub 1500 line rust init system for over a week. Hundreds of prompts. All with a local LLM running on my own GPUs because I expect to build with total sovereignty but also zero dependencies, no libc, no alloc, no std, and a test suite that proves the 20 implemented raw syscalls all use the right values by comparing against Linux kernel sources. This would be too annoying for a human to ever write code to standards this high, and would have taken me months to write by hand, but with the help of AI I was able to get it done and built in a way I can easily review and reason about. I have a memory safe baremetal tiny linux init now built to my exact requirements.
原话 · @匿名 · 来源 #comment_5
I'm somewhat surprised about PipePipe. I had a look on the commits of the various components and nothing looks out of place to me. Commits look rather reasonable, comments look useful and don't show obvious LLMisms. What are the AI smells there? It would be nice to expand a bit on the reasoning behind the verdicts.
原话 · @匿名 · 来源 #comment_1
I also noticed a pair of very bizarre apps, both branded with the yellow “Don’t tread on me” flag: DuressKeyboard & UnlicenseLauncher. What’s most curious is that they have been in development for quite some time, yet all the changes are done not with git but through the GitHub web file editor! Someone go find that person and teach them to use git.

免责声明:本卡片由 AI 从社区讨论中提炼,属于「痛点证据」,是需求分析与验证的起点,不等同于「已验证的市场需求」。AI 存在分析局限,关键决策前请打开上方原始讨论人工复核。