IIRC in other listed projects, once there was a policy permitting LLM generation under some condition, generated code did eventually get merged. Therefore, “permissive”.
There were more commits, the scanner basically checks the most recent history and stops, just to confirm that the project still allows LLMs. I don’t have a laptop or good internet right now to clone the entire repo and grep logs.
Before I refreshed it there were 4 flagged commits, all from September 1st. Since then there was one new LLM-assisted commit so it looks like the rate is decreasing.
That is good to know. I’ve also just checked the commits, and now I’m unsure if the LLM-related lines actually signified LLM use or just were copied from updated software changelogs. I will remove my above comment and stop with this topic until I learn more.
IIRC in other listed projects, once there was a policy permitting LLM generation under some condition, generated code did eventually get merged. Therefore, “permissive”.
Upd: it does look like the package manifests (needed to use the OS in practice) are increasingly LLM-assisted https://slopscan.ava.pet/repo/https%3A%2F%2Fgithub.com%2FNetBSD%2Fpkgsrc
On fedi I read that Drew DeVault is porting a fork of the Alpine ecosystem on top of the NetBSD core, which might be an answer to that.
Do those two commits count as “increasingly”?
There were more commits, the scanner basically checks the most recent history and stops, just to confirm that the project still allows LLMs. I don’t have a laptop or good internet right now to clone the entire repo and grep logs.
Before I refreshed it there were 4 flagged commits, all from September 1st. Since then there was one new LLM-assisted commit so it looks like the rate is decreasing.
That is good to know. I’ve also just checked the commits, and now I’m unsure if the LLM-related lines actually signified LLM use or just were copied from updated software changelogs. I will remove my above comment and stop with this topic until I learn more.