Measured false-positive rates

A dependency check that flags popular, legitimate packages gets ignored. So we measure how often ours do, on the most-used packages, and publish the result, the method and the blind spots. Last runs: 8 October 2026 (all measurements).

Want these checks on every pull request and for your AI coding agents? Presend for teams is a waitlist while we test demand.

Typosquat check (npm and PyPI)

The popular-package lists move. On 1 October, four packages that had recently entered the top 15,000 PyPI (djongo, tmol, orgparse, webp) were flagged; we checked each repository and added them to the reviewed list the same day.

Blind spot: only names close to a list of popular targets are checked. A name that an AI model invents and that resembles no real package (slopsquatting) is not caught by name similarity.

Against real malicious packages

Name similarity only catches malware that imitates a popular name. To see how much that is, we ran the typosquat check on the malicious packages recorded in OSV (OpenSSF malicious-packages advisories, withdrawn ones excluded), on 3 October 2026:

Most malicious packages do not imitate a popular name. On npm, many are internal company names published for dependency confusion, or spam. On PyPI, names that add a word to a target (requests-beta) are not caught by edit distance. The flagged ones aim at the expected targets: requests, beautifulsoup4 and colorama on PyPI, electron on npm. This is why the check is a triage signal to use alongside a malware scanner, not instead of one. Details and scripts: research/malicious-packages.

Publisher-change check (npm only)

Blind spots: it cannot see a hijacked account that keeps the same publisher name (as with ua-parser-js) or a malicious release by the original maintainer (as with colors.js). An attacker who has already taken over a popular package would pass the established-publisher rule. When the npm search API rate-limits us, the publisher check is reported as unavailable and the event stays flagged.

New-package signal (npm and PyPI)

A package first published less than 30 days ago is flagged new_package and the overall verdict becomes at least review_recommended: a name registered a few days ago deserves a look before it is installed. Measured on 8 October 2026, on the same lists:

Blind spots: on PyPI the age is that of the oldest file still on PyPI, so a project that deleted its earlier releases looks new. In our run, pikobs, an older project whose only remaining release had been uploaded the day before, was flagged for this reason. And age is no guarantee: an old package can still change hands or ship a malicious release.

Vulnerability check

Not a heuristic: it reports the OSV.dev advisories for the exact version you give. Without a version it reports advisories across all versions, which overstates the risk, so give the version you use.

Reproduce it

The code and test sets are in the public presend-source repository (Node.js, no dependencies):

node tests/typosquat/run.mjs                 # offline test set
node tests/typosquat/osv-malicious.mjs       # 1,023 real malicious packages, offline
node tests/typosquat/top-pypi.mjs            # top 15,000 PyPI (network)
node tests/typosquat/top-npm.mjs             # npm-high-impact (network)
node tests/maintainer-change/top-npm.mjs 200 # about 3 minutes (network)
node tests/package-age/measure.mjs 20000     # whole lists, about 14 minutes (network)
python3 research/malicious-packages/extract.py /tmp && node research/malicious-packages/measure.mjs /tmp   # about 240 MB
node research/malicious-packages/legit.mjs    # PyPI ranks 15,001-30,000 (network)

The typosquat and publisher-change scripts fail if a popular package is flagged without having been reviewed; the new-package script reports the counts by age. A regression test also fails if any of the 1,023 real malicious packages the typosquat check flagged on 3 October 2026 stops being flagged.

Install commands that point to unclaimed names

A separate measurement, of documentation rather than of our checks: how many npm READMEs of MCP and AI-agent packages run npx with a command name that nobody has registered. 80 of 4,830 on 8 October 2026.

Another one, of example apps: how many public examples and templates of funded developer-tool companies resolve a dependency with a critical advisory. 168 of 517, across 12 companies, in October 2026.

What both measurements mean for teams that publish install commands and examples, with a checklist: the code your users copy.

Contributions to other tools

Want the same measurement for your tool?

If you maintain a dependency-security tool and want its false-positive and detection rates measured the same way, write to presendapp@gmail.com.