These terms apply to every person who signs in to the PAR2 Labs portal at npm.par2labs.com, reads the documentation, or downloads or opens software from the private registry. They are between PAR2LABS PVT LTD, India ("PAR2 Labs", "we", "us") and you, and the organisation you work for ("your organisation"). By ticking the box when you first sign in, and again whenever we publish a new version, you confirm that you have read these terms, that you are authorised to accept them for your organisation, and that your organisation is bound by them.
The licence for the software you use (the Tessera Viz Free Edition Licence or the Tessera Viz paid licence, "your licence") is a separate document. These terms add to your licence. Where these terms and your licence both speak to the same thing, the stricter rule applies. In these terms "the Software" means every package, file, key, tool and update we deliver to you, in any form, including files you open with the unlock command ("unlocked files"), and "the Materials" means the Software, the documentation and everything else you can read or download on the portal and registry.
1. Your account #
1.1 One login belongs to one person. Each person has their own account, their own authenticator app and their own registry login. You may not share, lend, sell, publish or give away a login, a sign-in link, an authenticator device, a recovery code, a registry login, a token, a CI secret, a licence file or an activation code, not even to a colleague, a contractor or an affiliate.
1.2 Authorised users. Only individuals who work for your organisation, whom you have added in the portal, and who hold an account or a seat ("authorised users") may use the Materials under your licence. A contractor counts only while they work for your organisation on your own product and are bound in writing by terms at least as strict as these.
1.3 Second step. Signing in needs the link we email and the six-digit code from your authenticator app. Keep your recovery codes safe. We will never ask you for a code or a recovery code by email.
1.4 Your responsibility. What is done with a login is treated as done by its owner and by your organisation. You must tell us at once, and in any case within 72 hours, at security@par2labs.com if a login, device, code, token or CI secret is lost, used by someone else, or may have been exposed.
1.5 People leaving. You must remove a person from the portal, and stop their registry login and any CI secret they knew, on the day they stop working for your organisation or no longer need access. You must keep your list of authorised users correct.
1.6 Automation. You may use the official tools that we provide (the npm client with your own registry login, and @tesserify/cli) from your own computers and from your organisation's own build servers. You may not use scripts, bots, scrapers, proxies or any other automated means to read the portal or the documentation, to create accounts or logins, or to get around limits and blocks.
2. Software and the registry #
2.1 How the Software reaches you. Tessera Viz packages are delivered through the private registry, with your own registry login. We do not send a download of the whole product by other means unless we tell you so in writing.
2.2 Use inside your licence. You may install and use the Software only as your licence allows, for your own products and internal systems, within the number of seats, applications or institutions stated in your order, and only during the term of your licence.
2.3 No passing on. You may not publish, mirror, re-host, copy to another registry or package service, bundle for others, or share packages, tarballs, keys or unlocked files with anyone who is not an authorised user, whether for payment or free.
2.4 Unlocking. Paid packages are delivered in a protected form that opens only for a licensed seat or a CI secret of your organisation. You may open them only on your authorised users' computers and on your organisation's own build servers, and only to build and run your own product. You must keep unlocked files out of public repositories, out of shared repositories that people who are not authorised users can read, out of container images or archives you publish, and out of anything else you hand over.
2.5 Your own product. You may include the Software in your own product in the form that the official build process produces, so that the product works for your end users. You may not make the Software, or any part of it, available to others as a separate, reusable library, package, component, template or service, and you may not ship source maps, unminified copies or restructured copies of the paid code.
3. Protecting the Software #
3.1 No removing or getting around protections. You and your people may not remove, hide, change, disable, forge or get around: the licence check, the key service, the encryption of the Software, any licence or ownership notice or header in a file, any identifier or marking in the Software (visible or not), any limit or protection built into the Software, or any control of the portal or the registry. You may not build or use a tool for this, and you may not tell, help or enable anyone else to do it.
3.2 No extracting or analysing. You and your people may not reverse engineer, decompile, deobfuscate, disassemble, instrument, trace, dump from memory, or otherwise try to derive source code, algorithms, keys or protected logic from the Software, whether by hand or with automated tools, including AI tools, except to the extent the law allows despite this rule and then only after telling us in writing first.
3.3 No copying the idea. You and your people may not use the Software, the Materials or anything learned from taking them apart, to build, train, improve or support a product or service that competes with Tessera Viz, or to copy, reproduce or re-implement the Software.
3.4 AI tools. You may use AI coding assistants to help you build your own product with the Software, including the MCP server and the documentation pack that we provide to you. You may not give the Software's code files, unlocked files, keys or the documentation to any service or model to train it, fine-tune it, build an index or knowledge base that others can use, or to produce a copy or substitute of the Software.
3.5 Marking and identification. The Software may carry notices, identifiers and markings that name or point to your organisation or to a seat, some of which are visible and some of which are not. You agree to this. You may not look for, remove, alter, copy to other places, or forge them. If we find a copy of the Software or of a file from it where it should not be, we may use the markings, the records in section 5, and your account data, as evidence of where the copy came from, and we may share that evidence with a court, authority or adviser.
3.6 Benchmarks. You may not publish or share the results of performance tests or comparisons of the Software without our written consent.
3.7 Source of the Software. Nothing in these terms gives you source code or a right to receive it.
4. Documentation #
4.1 Each person may read the documentation that belongs to their plan, for their own work with the Software.
4.2 You may not copy the documentation except the code snippets that a page lets you copy, which you may use in your own software. You may not scrape, crawl, mirror or bulk download it with any tool or service, and you may not share any part of it with anyone outside your organisation, including by screenshot, photograph, print, paste or by giving it to an AI service.
4.3 You may not try to read pages that belong to a higher plan than yours.
4.4 We cannot make copying impossible, and we do not say we can. A browser has to receive the text to show it. The marks on pages and the limits we set make careless copying harder; the records in section 5 and these terms are what we rely on.
5. What we record #
5.1 We record: sign-ins and sign-in attempts; which documentation pages are read and when; downloads from the registry; requests for keys to open protected packages (which seat, which computer in a form we cannot read back, which package and version, when, and the outcome); your acceptance of these terms and of your licence; and the network address of these events (kept in a shortened or hashed form where we can).
5.2 We use these records to keep the portal secure, to check that licences are used as agreed, to give support, to find and stop misuse, to find out where a copy of our Software came from, and to prove and enforce our rights. We keep them for as long as we need them for these purposes and for a reasonable time after your licence ends. We do not sell them.
5.3 Every documentation page shows the reader's email address and the time as a faint mark. You agree to this.
5.4 You confirm that you have the right to give us the names and work email addresses of the people you add, and that you have told them that we process the records in section 5 for these purposes.
6. Compliance, checks and incidents #
6.1 Records and certificate. You must keep accurate records of who uses the Software, where it is installed or unlocked, and which build servers hold a CI secret. Within 30 days of our written request, and not more than once in any 12 months unless we have reason to suspect a breach, you must give us a written statement, signed by an officer of your organisation, that you comply with your licence and these terms.
6.2 Check. We may check your compliance from our own records at any time. If we have reasonable grounds to doubt your statement, we may, on 14 days' written notice and during normal working hours, review your records and the places where the Software is installed or unlocked, once in any 12 months, or at any time if we suspect a breach of section 2 or 3. We will keep what we learn confidential and will not disturb your business more than we need to.
6.3 Cost. We pay for our own checks. If a check finds that you used the Software outside your licence, or breached section 2 or 3, you pay the reasonable cost of the check and any fees that were not paid, within 30 days of our invoice.
6.4 Incidents. If you learn that the Software, unlocked files, a key, a token, a CI secret or the Materials have been lost, leaked, copied to a place they should not be, or accessed by someone who is not an authorised user, you must tell us within 72 hours at security@par2labs.com, stop the exposure, keep the logs, and help us find out what happened.
7. Updates and support #
7.1 During your licence term you may download new versions, receive the keys needed to open them, and open support requests.
7.2 When your licence ends or is suspended, access to the registry, to new versions, to keys and to support stops. You may still read the requests you already made. The community forum stays open to every signed-in person.
7.3 When your licence ends, you must stop using the paid Software and, within 30 days, delete or return all copies, including unlocked files, container images and backups that hold them, and give us a written statement, signed by an officer of your organisation, that you have done so. Files you already unlocked may keep working until you update, but you have no right to use them after the end of the term. No version you received gives you a right to use it after your licence has ended.
8. Breach, suspension, ending and remedies #
8.1 Suspension. If we find or reasonably suspect a breach of these terms or of your licence, we may suspend the person involved, or your whole account, at once and without notice. We will tell you why and what you can do to put it right.
8.2 Ending. We may end your access and your licence at once on notice if you breach section 1.1, 2 or 3, or if you do not put another breach right within 14 days of our notice. Sections that by their nature should continue after the end (including 3, 5, 6, 7.3, 8, 9, 10 and 11) continue.
8.3 Remedies. You accept that a breach of section 2 or 3 would harm us in ways money alone cannot repair. We may ask a court for an order that stops the breach (an injunction) without having to prove loss, in addition to any other remedy. If a court finds that you or your people breached section 2 or 3, you pay our reasonable legal costs and the profit you made from the breach.
8.4 Your people. You are responsible for everything your authorised users, and anyone who gains access through your credentials or your systems, do or fail to do under these terms.
8.5 The limit of liability in your licence does not apply to your breach of section 2 or 3, to your obligation to keep the Materials confidential, or to your infringement of our rights in the Software.
9. Ownership and confidentiality #
9.1 The Software and the Materials stay ours and our licensors'. You receive the rights your licence and these terms give, and no others.
9.2 The Software, the keys, the documentation and the contents of the portal and registry are our confidential information and contain our trade secrets. You must protect them with at least the care you give your own most sensitive information and never less than reasonable care. This duty lasts for as long as the information is not public through no fault of yours, and for at least five years after your licence ends.
9.3 If you give us feedback or suggestions, you allow us to use them freely without paying you and without naming you.
10. Our responsibility #
10.1 The portal, the registry and the documentation are provided as they are, and may be unavailable from time to time. The warranty disclaimer and the limitation of liability in your licence also apply to the portal, the registry and the documentation, subject to section 8.5.
10.2 Nothing in these terms limits a right that the law gives you and that cannot be limited.
11. General #
11.1 New versions. When we publish a new version of these terms or of your licence, the portal asks you to accept it at your next sign-in. Until you accept, you cannot use the account pages, the documentation, the registry login or support. A new version does not apply to what you did before you accepted it.
11.2 Changes to the service. We may change or end the portal or registry with reasonable notice. You may stop using them at any time.
11.3 Assignment. You may not transfer your rights under these terms or your licence to anyone else, by sale, merger, change of control or otherwise, without our written consent. You must tell us in writing within 14 days if your organisation changes owner.
11.4 Parts that cannot be enforced. If a part of these terms cannot be enforced, the rest stays in force, and the part is read as narrowly as it needs to be to be enforceable.
11.5 Waiver. If we do not enforce a right straight away, we do not give it up.
11.6 Notices. We may give notice by email to the administrator of your account or to the address in your order. You may write to us at the address in section 12.
11.7 Whole agreement. These terms and your licence are the whole agreement between us about the portal, the registry and the Software, and replace earlier statements about them.
11.8 Law and courts. These terms are governed by the laws of India. The courts of India have exclusive jurisdiction over disputes about them, as in the Tessera Viz licence.
12. Contact #
PAR2LABS PVT LTD, India. Questions and licensing: contact@par2labs.com. Security reports, lost logins and incidents: security@par2labs.com.