Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command to list copyright holders/summary printout #68

Open
xd009642 opened this issue Dec 5, 2019 · 2 comments
Open

Command to list copyright holders/summary printout #68

xd009642 opened this issue Dec 5, 2019 · 2 comments

Comments

@xd009642
Copy link

xd009642 commented Dec 5, 2019

So as well as the license text for my companies own compliance we have to have a section beforehand with the list of dependencies and the copyright holders. I'm aware this may be slightly more niche so as an alternative I'm sure a lot more people could benefit from a summary of the project name, license, copyright-holder without the full license text.

Come to think of it exporting to some form of output like xml (or something nicer) with all the fields (including full license text) would make it easy to automatically generate any documents required by different companies compliance departments.

Also, super impressed with the ease of cargo-lichking. The comparative process for python and C++ projects was painful to say the least :)

@Nemo157
Copy link
Owner

Nemo157 commented Dec 6, 2019

By copyright holder I presume you mean the actual copyright holders, not just the authors listed in the crate metadata or license files that have them?

That would be significantly more complicated, the only really machine-readable source is probably the repository history, so would require parsing the package.repository field, downloading the repo (which may not be exactly at the url in the field) and getting a list of authors from that. Luckily the Rust ecosystem is very git-centric so supporting git only would probably get 99% of dependencies working.

@xd009642
Copy link
Author

xd009642 commented Dec 6, 2019

I was just thinking in the license files that have them or crate metadata as getting it from the repository history could be a massive pain. Both would be useful to different people I imagine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants