org.daisy.pipeline.build:modules-test-helper

Artifact:

latest

The DAISY Consortium is an international association that develops, maintains and promotes international DAISY (Digital Accessible Information System) Standards. It is managed by a Board made up of representatives from all Full Member organizations. The Consortium is constituted as a not-for-profit association under Swiss law and is governed by Articles of Association.

License: Weak Copyleft (LGPL-3.0-only)

Published:

See on Maven

SAFE Assessment

Compliance

Licenses

1 software distribution restrictions

Secrets

No sensitive information found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

No application hardening issues

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

Overview issues1 vulnerabilities0 malware0 behaviors13 dependencies9 contributors1 versions16

Popularity

N/A

Total Downloads

Contributor

Declared Dependencies

Dependents

Top issues

See all issues

Problem

Software license is a legal instrument that governs the use and distribution of software source code and its binary representation. Software publishers have the freedom to choose any commonly used or purposefully written license to publish their work under. While some licenses are liberal and allow almost any kind of distribution, with or without code modification, other licenses are more restrictive and impose rules for their inclusion in other software projects. Some software licenses place restrictions on software distribution of the code they apply to. These restrictions may extend to the services built upon the code licensed under such restrictive licenses. Some restrictive licenses explicitly state that the licensee may not provide the software to third parties as a hosted or managed service, where the service provides users with access to any substantial set of the features or functionality of the licensed software. When building commercial applications, this is typically undesirable. Therefore, the inclusion of any code that may impose limits on software distribution is commonly avoided or even prohibited by the organization policy.

Prevalence in Maven community

No prevalence information at this time

Next steps

Confirm that the software package references a component or a dependency with a restrictive license.

Consider replacing the software component with an alternative that offers a license compatible with organization policy.