You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 3, 2022. It is now read-only.
Given a piece of software under consideration, the provenance (aka. origin and license) of every third-party components included in that software should be well known and eventually disclosed by the provider.
The benefits are obvious: knowing the license is essential to be allowed to use the code; and knowing the detailed origin is important to evaluate the originality, quality and eventual bugs or security issues related to the software under consideration.
For that there are a few good free and open source tools that can help uncover provenance data:
Here is a suggestion for this policy:
Given a piece of software under consideration, the provenance (aka. origin and license) of every third-party components included in that software should be well known and eventually disclosed by the provider.
The benefits are obvious: knowing the license is essential to be allowed to use the code; and knowing the detailed origin is important to evaluate the originality, quality and eventual bugs or security issues related to the software under consideration.
For that there are a few good free and open source tools that can help uncover provenance data:
The text was updated successfully, but these errors were encountered: