lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

64
active users

#vibecoding

5 posts4 participants0 posts today

> [there is a] new type of threat to the software supply chain: package hallucinations. These hallucinations, which arise from fact-conflicting errors when generating code using LLMs, represent a novel form of package confusion attack that poses a critical threat to the integrity of the software supply chain.

arxiv.org/abs/2406.10279
theregister.com/2025/04/12/ai_

arXiv logo
arXiv.orgWe Have a Package for You! A Comprehensive Analysis of Package Hallucinations by Code Generating LLMsThe reliance of popular programming languages such as Python and JavaScript on centralized package repositories and open-source software, combined with the emergence of code-generating Large Language Models (LLMs), has created a new type of threat to the software supply chain: package hallucinations. These hallucinations, which arise from fact-conflicting errors when generating code using LLMs, represent a novel form of package confusion attack that poses a critical threat to the integrity of the software supply chain. This paper conducts a rigorous and comprehensive evaluation of package hallucinations across different programming languages, settings, and parameters, exploring how a diverse set of models and configurations affect the likelihood of generating erroneous package recommendations and identifying the root causes of this phenomenon. Using 16 popular LLMs for code generation and two unique prompt datasets, we generate 576,000 code samples in two programming languages that we analyze for package hallucinations. Our findings reveal that that the average percentage of hallucinated packages is at least 5.2% for commercial models and 21.7% for open-source models, including a staggering 205,474 unique examples of hallucinated package names, further underscoring the severity and pervasiveness of this threat. To overcome this problem, we implement several hallucination mitigation strategies and show that they are able to significantly reduce the number of package hallucinations while maintaining code quality. Our experiments and findings highlight package hallucinations as a persistent and systemic phenomenon while using state-of-the-art LLMs for code generation, and a significant challenge which deserves the research community's urgent attention.
Continued thread

En qué consiste el Slopsquatting:

Un desarrollador se apoya en una IA (LLM) para generar código para su proyecto. Pongamos por ejemplo que usa JavaScript.

La IA se inventa un paquete de npm que en realidad no existe. Pongamos que lo ha llamado "RxTs". (esta es la parte del slop)

Un actor malicioso, vé que la IA suele inventarse este paquete ficticio, y se crea un malware que sube a los repositorios oficiales de npm con este mismo nombre. (Esta es la parte del squatting)

El usuario se fija que la IA ha añadido un paquete que no tiene instalado, lanza un npm install para que ese paquete se descargue de los repositorios oficiales y así pueda utilizarlo.

Pongamos que el actor malicioso quiere pasar desapercibido e incluso hace que dicho paquete, efectivamente, haga lo que la IA ha dicho que hace.

El paquete malicioso está en tu aplicación, instalado, funciona, incluso ha solucionado tu problema, si no te das cuenta es posible que termine incluso en producción infectando a vete a saber cuántos sistemas y máquinas de tu entorno y teniendo acceso a vete a saber qué datos de tu aplicación o usuarios.

There is no Vibe Engineering
—Sergey Tselovalnikov

"#vibecoding only covers coding at a single point in time. If an agent is used to generate a quick prototype and validate it with tests, that’s coding – not engineering. Engineering means designing systems capable of withstanding real-world conditions, sustaining workloads, resisting security threats, migrating and supporting users’ data in the system, and adapting to new requirements often many years down the line"

serce.me/posts/2025-31-03-ther

There is no Vibe Engineering · There is no Vibe EngineeringThis article explores the relationship between vibe coding and software engineering.
Continued thread

As of March 2025 I'd say #vibecoding is cool to get projects started, and I really appreciate that I don't have to read the plotly library, but I'm doubtful it will lead to a sustainable project.

Let's see when I find the time to integrate other platoforms data for comparison.

First I was like, "Vic, you're probably being too pessimistic about vibe coding and digital #accessibility ," but then I was like, "This is the year of adding journos to war plan group chats, don't tell me about pessimism," and so I hit publish.
#a11y #VibeCoding

cost-chef.ski/2025/03/29/10-re

cost-chef.ski10 reasons why vibe coding is (probably) bad news for digital accessibility – Vic Kostrzewski – Learning Designer, Translator, Project Manager, Publisher.