Nuget Package

JsonPath.Net

Package Version

3.0.1

Operating System

None

.Net Target (if relevant, please specify the version in the description)

None

A clear and concise description of the bug. Include what you're experiencing and how that compares with what you expect.

The EULA of the project doesn't completely match what's on the Open Source Maintenance Fee website and info provided by maintainers under #987.

Sorry to be a bother about this again, and I hate to play lawyer. However, we use JsonPath.Net in Orchard Core, a fellow .NET Foundation project, and it also has users that are picky about legal matters, so we'd like to be unambiguously clear here.

Key concerns of the Orchard Core maintainers:

• The trigger/definitions are unclear: “User” and “generate revenue by the Software” aren’t defined, making applicability to commercial use ambiguous.
• It does not clearly exclude transitive/indirect use (e.g., consuming the library via another OSS dependency).
• This creates legal/compliance risk: scope/enforcement is uncertain, and the EULA suggests terms apply by “accessing or using” the binary packages.

Can you please update the EULA to include what was communicated about the new terms informally? Thank you!

Please add test code or steps to reproduce the behavior.

Not applicable.

Is there any other information you'd like to share regarding this bug?

No response

Are you representing an organization or employer? If so, who?

Orchard Core

Code of Conduct & Contributor Guidelines

• I agree to follow this project's Code of Conduct and Contribution Guidelines.