A trial license. You may evaluate the software for less than 32 days in a row. Keeping it after that needs a license from the publisher.
On this page
What it does
The PolyForm Free Trial License 1.0.0 grants one purpose and one only: use to evaluate whether the software suits a particular application, for less than 32 consecutive calendar days, on behalf of you or your company. Inside that window you may do what copyright would otherwise stop you doing, and you may make changes and new works while you try it out. You may not distribute copies of the software. The license is written for a paid product that ships a trial build, so the expected next step is a commercial license from the publisher.
Details
Two details decide most reviews. The window is 32 consecutive days, counted from when the evaluation starts, and it is tied to evaluating one particular application rather than to general use. And this license has no repair window: the other PolyForm licenses let you put a first violation right within 32 days, while here every license ends the moment you step outside the terms. A trial build that stayed in a lockfile after the evaluation is the case to look for.
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
Trial use
Use to evaluate whether the software suits a particular application, for less than 32 consecutive days.
Modify
You may make changes and new works while you evaluate the software.
Patent use
The grant covers the patent claims the licensor can license that your use would infringe.
Limits
Use past day 32
The permitted purpose is an evaluation shorter than 32 consecutive days. Use past that point needs another license.
Distribute
You may not distribute copies of the software. The trial covers your own evaluation.
Hold liable
The authors disclaim warranty. Recipients cannot hold them liable for damages arising from the software, except where law forbids that disclaimer.
Obligations
Buy it or remove it
When the evaluation ends you need a license from the publisher, or the package has to go.
No repair window
This license has no cure period. If you step outside the terms, every license ends at once.
What PolyForm-Free-Trial-1.0.0 requires when you ship
PolyForm-Free-Trial-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.
You are evaluating whether the software suits a particular application, rather than using it as part of your normal work.
The evaluation is shorter than 32 consecutive calendar days, and you know the date it started.
You do not distribute copies of the software, and it is not part of anything you hand to a customer.
You bought a license from the publisher, or removed the package, before the window ran out.
The duties named in PolyForm-Free-Trial-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.
Buy it or remove it
When the evaluation ends you need a license from the publisher, or the package has to go.
No repair window
This license has no cure period. If you step outside the terms, every license ends at once.
Things to be aware of
- Teams keep a trial build in the lockfile long after the evaluation. The grant ran out on day 32, and nothing in the file says so.
- Teams expect the same repair window as the other PolyForm licenses. This one has none. A violation ends every license at once.
- Teams read 32 days as 32 days of use. The text counts consecutive calendar days from the start of the evaluation.
What the PolyForm Free Trial License 1.0.0 does not do
Search results often flatten PolyForm Free Trial License 1.0.0 into a slogan. These are the usual misreads. PolyForm-Free-Trial-1.0.0 is a grant with conditions, not a permission to skip the paperwork below.
- PolyForm Free Trial is not an open source license. It is a time-limited evaluation grant, and it ends by itself.
- It does not let you distribute the software, and it does not cover production use once the evaluation window has passed.
How PolyForm-Free-Trial-1.0.0 differs from nearby licenses
These licenses are often confused with PolyForm-Free-Trial-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-Free-Trial-1.0.0
- A trial license. You may evaluate the software for less than 32 days in a row. Keeping it after that needs a license from the publisher.
- PolyForm-Internal-Use-1.0.0
- Use inside your own company is allowed, including changes. Passing the software on to anyone outside it is not. This is not open source.
- 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 Free Trial License 1.0.0
Answers to common questions about what PolyForm Free Trial License 1.0.0 requires, when its duties apply, and what evidence belongs with a release.
What is the PolyForm Free Trial License 1.0.0?
The PolyForm Free Trial License 1.0.0 grants one purpose and one only: use to evaluate whether the software suits a particular application, for less than 32 consecutive calendar days, on behalf of you or your company. Inside that window you may do what copyright would otherwise stop you doing, and you may make changes and new works while you try it out. You may not distribute copies of the software. The license is written for a paid product that ships a trial build, so the expected next step is a commercial license from the publisher.
What does PolyForm-Free-Trial-1.0.0 require when you ship a product?
You are evaluating whether the software suits a particular application, rather than using it as part of your normal work. The evaluation is shorter than 32 consecutive calendar days, and you know the date it started. You do not distribute copies of the software, and it is not part of anything you hand to a customer. You bought a license from the publisher, or removed the package, before the window ran out.
Is PolyForm-Free-Trial-1.0.0 open source?
Not in the OSI sense. PolyForm-Free-Trial-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-Free-Trial-1.0.0 different from PolyForm Internal Use License 1.0.0?
PolyForm-Free-Trial-1.0.0 asks this: A trial license. You may evaluate the software for less than 32 days in a row. Keeping it after that needs a license from the publisher. PolyForm Internal Use License 1.0.0 asks this: Use inside your own company is allowed, including changes. Passing the software on to anyone outside it is not. This is not open source. Open the PolyForm Internal Use 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-Free-Trial-1.0.0 for a buyer?
The catalog records PolyForm-Free-Trial-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. SourceTrust does not track the end of a trial window for you. Record the date the evaluation started where the person who upgrades the dependency will see it.
Where do I record PolyForm-Free-Trial-1.0.0 for a buyer?
The catalog records PolyForm-Free-Trial-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. SourceTrust does not track the end of a trial window for you.
Record the date the evaluation started where the person who upgrades the dependency will see it. Read /docs/reviewing-component.
Related licenses
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.