Skip to main content
SourceTrust
See other licenses

PolyForm-Perimeter-1.0.0

PolyForm Perimeter License 1.0.0

Any purpose is allowed except giving others a product that competes with the software. Notices travel with every copy. Not open source.

On this page

What it does

The PolyForm Perimeter License 1.0.0 is the open end of the PolyForm family. Any purpose is a permitted purpose, except providing others a product that competes with the software. Inside that line you may use it commercially, change it, build new works from it and distribute copies, including copies carrying your changes. The license explains what competing means: if you market a product as a substitute for the functionality or value of the software, it competes, whatever shape it takes. A service, a library, a plug-in, a port to another platform or language, and a free product can all compete.

Details

Perimeter draws its line around one product: the software itself. Shield, its sibling, draws the line wider and takes in the other products the publisher builds on the software. So a review of a Perimeter package is a short question. Are you selling, or giving away, something that a buyer would take instead of this software? If the answer is no, the grant is wide, and what is left is the notice work. Every copy you pass on must carry the terms or their address, plus any Required Notice lines the publisher shipped.

What it allows and requires

Choose a category to see the full grant in one scannable list. Permissions show what the license allows, limits show what it withholds, and obligations show the conditions your release process must satisfy.

Permissions

  • Commercial use

    You may use the software commercially, and sell a product you build with it.

  • Modify

    You may make changes and new works for any permitted purpose.

  • Distribute

    You may distribute copies, including copies carrying your own changes.

  • Patent use

    The grant covers the patent claims the licensor can license that your use would infringe.

What PolyForm-Perimeter-1.0.0 requires when you ship

PolyForm-Perimeter-1.0.0 is readable source with use limits. The work is to match your use to the written grant, then keep the text on the record so procurement can read it. Do not treat a source-available identifier as OSI-style open source because the code is on GitHub.

  1. You are not providing others a product that a buyer would take instead of this software, whether you charge for it or give it away.

  2. You have looked past the shape of your product. A service can compete with a library, and a port to another language still competes.

  3. Anyone who gets any part of the software from you also gets the license terms, or the address where they can read them.

  4. You pass on every plain-text Required Notice line the publisher shipped with the software, word for word.

  5. You have made no patent claim about the software, because a written claim ends your patent license at once.

The duties named in PolyForm-Perimeter-1.0.0

The written grant is the source of the limits. These rows are the usual conditions teams have to match against their actual use, then keep on the record.

Include license

Anyone who gets any part of the software from you also gets these terms, or their address.

Include notice

Pass on every plain-text Required Notice line the publisher shipped with the software.

Fix within 32 days

After a first written notice you keep your licenses if you put things right within 32 days.

Things to be aware of

  • Teams read a competing product as a copy of the software. The text is wider. Marketing anything as a substitute for its value is enough.
  • Teams assume a free tool cannot compete. The license says a product competes even when it is provided free of charge.
  • Teams miss the Required Notice lines. They sit in the files the publisher shipped, and they have to travel with every copy you pass on.

What the PolyForm Perimeter License 1.0.0 does not do

Search results often flatten PolyForm Perimeter License 1.0.0 into a slogan. These are the usual misreads. PolyForm-Perimeter-1.0.0 is a grant with conditions, not a permission to skip the paperwork below.

  • PolyForm Perimeter is not an open source license. A ban on competing products is a limit on the field of use, which open source does not allow.
  • It does not stop you selling your own product built with the software. It stops you offering something people would take instead of the software.

How PolyForm-Perimeter-1.0.0 differs from nearby licenses

These licenses are often confused with PolyForm-Perimeter-1.0.0, but their release duties differ. Each row summarizes what the license requires when you ship. Open the linked page for the full checklist.

PolyForm-Perimeter-1.0.0
Any purpose is allowed except giving others a product that competes with the software. Notices travel with every copy. Not open source.
PolyForm-Shield-1.0.0
Like Perimeter, with a wider limit. You may not compete with the software or with the products the publisher builds on it.
PolyForm-Small-Business-1.0.0
PolyForm Small Business allows commercial use only under the employee-count cap in the text. Larger companies need a separate license.
source-available
You can read the code. That is not the same as permission to use it any way you like. Source available is not open source.

Common questions about PolyForm Perimeter License 1.0.0

Answers to common questions about what PolyForm Perimeter License 1.0.0 requires, when its duties apply, and what evidence belongs with a release.

What is the PolyForm Perimeter License 1.0.0?

The PolyForm Perimeter License 1.0.0 is the open end of the PolyForm family. Any purpose is a permitted purpose, except providing others a product that competes with the software. Inside that line you may use it commercially, change it, build new works from it and distribute copies, including copies carrying your changes. The license explains what competing means: if you market a product as a substitute for the functionality or value of the software, it competes, whatever shape it takes. A service, a library, a plug-in, a port to another platform or language, and a free product can all compete.

What does PolyForm-Perimeter-1.0.0 require when you ship a product?

You are not providing others a product that a buyer would take instead of this software, whether you charge for it or give it away. You have looked past the shape of your product. A service can compete with a library, and a port to another language still competes. Anyone who gets any part of the software from you also gets the license terms, or the address where they can read them. You pass on every plain-text Required Notice line the publisher shipped with the software, word for word. You have made no patent claim about the software, because a written claim ends your patent license at once.

Is PolyForm-Perimeter-1.0.0 open source?

Not in the OSI sense. PolyForm-Perimeter-1.0.0 is source-available: you can read the code, but the grant restricts how you may use it. Read the actual text.

How is PolyForm-Perimeter-1.0.0 different from PolyForm Shield License 1.0.0?

PolyForm-Perimeter-1.0.0 asks this: Any purpose is allowed except giving others a product that competes with the software. Notices travel with every copy. Not open source. PolyForm Shield License 1.0.0 asks this: Like Perimeter, with a wider limit. You may not compete with the software or with the products the publisher builds on it. Open the PolyForm Shield License 1.0.0 page for what that license requires when you ship. Do not treat the SPDX ids as interchangeable because the short names look similar.

Where do I record PolyForm-Perimeter-1.0.0 for a buyer?

The catalog records PolyForm-Perimeter-1.0.0 as source available, and as a license a network deployment does not clear. A network distribution review item therefore appears on the checklist for SaaS and mixed projects, and publishing stays blocked until a person confirms it. The identifier is a templated one, so the fetch never lands it on confirmed, and the text found in the package is put in front of you. SourceTrust does not collect the publisher's Required Notice lines for you yet, so read them in the package.

Where do I record PolyForm-Perimeter-1.0.0 for a buyer?

The catalog records PolyForm-Perimeter-1.0.0 as source available, and as a license a network deployment does not clear. A network distribution review item therefore appears on the checklist for SaaS and mixed projects, and publishing stays blocked until a person confirms it.

The identifier is a templated one, so the fetch never lands it on confirmed, and the text found in the package is put in front of you. SourceTrust does not collect the publisher's Required Notice lines for you yet, so read them in the package.

Read /docs/reviewing-component.

See also

The hub is the pillar for this cluster. Sibling licenses are the other spokes. Product FAQ links explain how SourceTrust records the duty, not the license text itself.

Practical guidance for procurement review, not legal advice. Confirm high-stakes use with counsel.

Ship the proof.

Import PolyForm Perimeter License 1.0.0 and the rest of what you ship. Free to import and review. You only pay when you publish.

Start for free

Cookies on sourcetrust.dev

We use essential cookies for security, including abuse prevention on our site scan and walkthrough request form. With your permission, we also use optional analytics and diagnostics (Google Tag Manager on this site, and the Sentry browser SDK on the SourceTrust application when configured). See our cookie policy.