The threat is new, so here is the shape of it. AI coding assistants
now help millions of programmers decide which small pieces of
open-source code to pull into a project. Sometimes an assistant gets
confident and invents the name of a useful-sounding package
that does not actually exist. An attacker who is watching can publish malware
under that exact name within minutes. The next person who trusts the
suggestion installs it without ever suspecting anything was wrong.
Argand answers this in five layers, all of which run before you type a
query.
Layer T0 checks that the package is real. When
anything asks Argand for a code package, whether it is a person, an AI
assistant, or another service, Argand confirms the package actually exists on its official source before it hands back
the name. Imagined packages get filtered out before they ever reach
you, so a name that was never published has no way to slip through.
Layer T1 shows you the risk facts upfront. Every code
package Argand shows arrives with a set of plain signals attached.
You can see how new the package is, how its maintainers have behaved
over time, whether its downloads are climbing or crashing, whether the
name sits suspiciously close to a far more popular package, whether
ownership changed hands recently, and whether it matches anything
already known to be malicious. You see exactly what Argand sees, with
nothing hidden.
Layer T2 gives anything suspicious extra scrutiny, and never
buries it silently. A package that looks suspect is passed
through quick rules first. If it gets past those, a small
machine-learning model trained on known-bad examples takes a look. A
careful AI second opinion is held in reserve for the harder cases.
Whatever the verdict turns out to be, Argand labels the
result instead of quietly deleting it, so you can always see what was
flagged and the reason behind it.
Layer T3 keeps brand-new packages from being
auto-recommended to AI assistants. When an assistant asks
Argand for a recommendation, Argand will not suggest a package that
has not yet crossed a real usage floor. The floor is at least a thousand downloads a week. You can still
search for a brand-new package yourself and find it. It simply will
not be handed to an assistant until real people have been using it for
a while.
Layer T4 catches bad actors later too. Packages
Argand already trusts get re-checked constantly against fresh security
advisories, takedown notices, and signals like a sudden change of
owner. If something that used to be safe goes bad after Argand picked
it up, it is demoted or removed right away. The cleanup does not wait
for some quarterly sweep.
All five layers do their work before you ever type a query, so they
cost nothing at search time. The upshot is plain. People and the
assistants helping them both end up safer, while an attacker who tries
to slip something past Argand finds that it is not a free shot.