Every package is read before you run it
When a seller uploads a package it is unpacked and every source file in it is analysed. Four things are looked for. If any of them is found, the package is not listed.
Malware and credential theft
Every source file is read for code that exfiltrates data, phones home, drops a payload, or harvests environment variables and keys. Obfuscated or minified code that cannot be reasoned about is treated as a finding rather than waved through.
Prompt injection aimed at your AI agent
If you paste a package into a coding agent, every comment, README and string in it is something that agent will read. Instructions hidden in that text, telling a model to ignore its rules, exfiltrate a key or rewrite unrelated files, are looked for specifically. No comparable marketplace checks for this.
Build integrity
Imports that do not resolve, dependencies missing from the manifest, syntax that will not parse, configuration referenced but not shipped. The errors that turn "clone and run" into an afternoon.
Original work
Structural fingerprints of the package are matched against 230,000+ fingerprints: a reference corpus drawn from public code, plus every other package already listed here. Matching is structural rather than textual, so renaming the variables and reformatting the file does not disguise a package that was taken from somewhere else.
The prompt-injection check is the one most people have not met before. What it looks like and how to check for it yourself.
What the review deliberately does not do
It reads the source. It does not execute your build or run the test suite, and every report it writes says so. So it cannot promise a package is free of bugs, and this page will not pretend otherwise. Nothing that reads code can make that promise.
What covers you is what happens afterwards. A package that will not build or run, or that is missing something the listing advertised, is refundable in full with no fees deducted, provided you report it within 48 hours of buying it. Separately, 3 buyer reports put the seller on a 7-day clock to fix it or lose the listing.
Common questions
Does review guarantee the code works?
No, and nothing that reads code could. The review analyses source; it does not execute your build or run the test suite, and every report says so. What covers you instead is the reporting route: if a package will not build or run, or is missing something the listing advertised, report it within 48 hours of buying it. We re-run verification against the package you received, and if that confirms the failure you are refunded in full as store credit with no fees deducted, or to your card if you would rather, which takes longer.
What happens if a package breaks later?
Report it. Once 3 separate buyers have reported the same listing, the seller has 7 days to publish a fix that passes review, or the listing comes off sale. Your own copy is never taken away, and the fixed version costs you nothing.
Who reviews the packages?
An automated reviewer reads every source file in the uploaded archive. Reviews run on a daily schedule rather than sitting in a manual queue, so a submission is usually resolved within a day rather than a fortnight.
Can I see the review before I buy?
Yes. Every listing shows what its package was checked for and what was found, before you buy rather than after.
What happens to a package that fails?
It is not listed. The seller is told what was found and can fix it and resubmit. A failure on a new version never affects the version already on sale: buyers keep downloading the current one until a replacement passes.