opensanctions

v0.1.0Verified publisher

Screens a person's or company's name against OpenSanctions: sanctions lists, politically exposed persons, watch lists

Report a problem

Say what's wrong with opensanctions, and the report goes where it can be fixed: a problem with the tool to its public Issues, malware and abuse privately to the registry's reviewers.

What's wrong? It doesn't work It fails, crashes, hangs, or finds nothing on a value it should handle. It shows an error It stops with an error message. You can paste the message, minus anything personal. It's out of date Its project has released a newer version than the registry has. Something on this page is wrong Its inputs, outputs, keys, or what a run contacts. Malware, abuse or a legal problem Goes privately to the registry's reviewers, not to the public.

What happens next

It doesn't work, shows an error or is out of date

Signed in, your report is an issue on the package's Issues tab. Its maintainers hear about it at once, others can say they have the same problem, and you hear when it changes.
Without an account it is only counted, once per address a day. Three reports in a week open an issue marked unconfirmed, until someone reproduces it.

Malware, abuse or a legal problem

A reviewer reads it within 72 hours, or 24 hours for malware or credible harm.
Possible actions, in order of weight: dismiss, ask the publisher to fix, yank the version, remove the package, suspend the namespace, ban the account.
Malware: removal, a warning to everyone who installed it, a suspended namespace, and an advisory on the transparency page.
Every removal is listed there with its reason category; report counts are published each quarter.

Reports without an account are rate-limited. The acceptable-use policy says what isn't allowed. For vulnerabilities in the registry or in ot itself, email security@otinstaller.com.