iTechVistaMARKETPLACE
Sell code

Reporting infringing code

If something listed here is your work, or uses your work in a way its licence does not allow, this is how to tell us and what we do about it.

Last updated 17 August 2026

The short version

  • •Email support@itechvista.com with the subject line Infringement report. You do not need an account.
  • •We acknowledge within two business days and aim to decide within five.
  • •A listing we judge to infringe is removed from sale, and buyers who already downloaded it are notified.
  • •Sellers get to answer before a final decision, unless the copying is obvious, in which case the listing comes down first and the seller answers afterwards.

1. Who can report

Anyone. You do not have to be a customer, a seller, or signed in. If you hold the rights, or act for someone who does, that is enough to open a report.

Signed-in users can also report a listing directly from its page, which is the faster route for the ordinary case of a package that is broken or misdescribed. That route is built for product complaints and escalates on volume. An infringement claim is not a product complaint and is not decided by counting reports, so please use the email route below instead.

2. What to send

Copy the template into an email to support@itechvista.com. It is short on purpose. We would rather have a report with a gap in it than no report.

To: support@itechvista.com
Subject: Infringement report

1. The listing
   URL:
   Package name:

2. What of mine it infringes
   Title of the work:
   Where the original can be seen (URL, repository, package registry):
   What licence it is under, if any:

3. What specifically was taken
   Files, functions or sections, as precisely as you can:

4. Who you are
   Name:
   Company, if any:
   Email:
   Your relationship to the work (owner / employee / agent / lawyer):

5. Statements
   I believe in good faith that the use described above is not
   authorised by the rights holder, its agent, or the law.
   The information in this report is accurate.
   Signed:
   Date:

Point 3 is the one that decides how fast this moves. "They copied my library" takes us a long time to check. "Their src/auth/session.ts is my lib/session.ts with the names changed" takes minutes.

3. What happens next

  • •We acknowledge within two business days and tell you who is handling it.
  • •We look at the code. Every package here is fingerprinted when it is published and compared against a corpus, so we can often confirm or dismiss copying quickly and without your help.
  • •We put it to the seller with your report attached, minus your contact details unless you tell us to include them, and give them a short window to answer.
  • •Where the copying is plain, the listing is suspended first and the seller answers afterwards. Leaving obviously infringing code on sale while a conversation happens is not a neutral act.
  • •We decide and tell you. If we take it down, it is removed from sale, existing buyers are told, and their downloads stop. If we do not, we say why.

4. What we do not do

We do not adjudicate contested licence interpretations. If two people disagree in good faith about whether an MIT-licensed file was attributed properly, that is a dispute between them, and we will say so rather than pretend to be a court. What we will do is remove the listing while it is unresolved if the risk to buyers is real.

We also do not act on anonymous reports about competitors. Point 4 of the template is not decoration.

5. If you are the seller

You will be told what was claimed and given a chance to answer before a final decision, except in the plain-copying case above. If you believe the report was wrong, reply with the provenance of the code: the repository history, the licence you relied on, or the commission that produced it. A listing suspended in error is restored, and no commission is charged on sales that never happened.

Publishing code you do not have the right to sell breaches our terms and is grounds for removing the account and withholding the proceeds of those sales.

6. A note on the DMCA

This page is not a DMCA policy, and we do not claim the safe harbour under 17 U.S.C. 512. That protection requires a designated agent registered with the U.S. Copyright Office, and we have not made that registration. Claiming a protection we do not hold would be worse than not claiming it.

What we do instead is described above: a way in that does not require an account, a person who reads it, and a listing that comes down when it should. If you would ordinarily send a formal takedown notice, send it to the same address and we will act on it.

Back to iTechVista