Trademark policy

1The license is not the name

The AGPL-3.0 and the commercial license grant rights to the code. They do not grant the right to use the tcpcat name or logo to present your own product. The name identifies where the software comes from; this page explains how it may be used.

The name is used by Nicolas Blondelle (NycolazSec) to identify this project. No trademark registration is claimed on this page.

2Always fine

• Saying that your tool, report or service uses or is compatible with tcpcat (“scan performed with tcpcat”, “imports tcpcat JSON”).
• Redistributing an unmodified tcpcat under its own name, with its license notices intact.
• Writing articles, tutorials, talks, reviews or packages that refer to tcpcat by name.
• Linking to the project: github.com/NycolazSec/tcpcat and tcpcat.io.

3Needs written permission

• Naming a modified fork or a derived product “tcpcat” (or something easily confused with it). Please pick your own name and say it is “based on tcpcat”.
• Presenting your product, company or service as official, endorsed or partnered with tcpcat.
• Using the name or logo in a product name, domain name, app-store listing or social handle.
• Shipping tcpcat inside a commercial product under the tcpcat name: this also requires the commercial (OEM) license.

4Licensing notices must stay

Whatever you build on tcpcat, the copyright and license notices must be kept, and under the AGPL the corresponding source must be made available to the people who receive or use your version. The binary prints its terms with tcpcat --license.

5Ask, or report a misuse

Not sure whether your use is fine, or you came across a product that seems to use tcpcat without following these terms? Write to us: