cargo-about icon indicating copy to clipboard operation
cargo-about copied to clipboard

📜 Cargo plugin to generate list of all licenses for a crate 🦀

Results 27 cargo-about issues
Sort by recently updated
recently updated
newest added

**Is your feature request related to a problem? Please describe.** Not exactly a problem, but our use case is generally "gather license information and put it in a spreadsheet" so...

enhancement
hacktoberfest

`cargo about generate` stops looking for licenses after it finds a license which was not accepted. This is especially annoying when working with many files as the current iteration approach...

enhancement

**Is your feature request related to a problem? Please describe.** For our CI I would like the execution of `cargo-about` to return an error code if there are any warnings...

enhancement

**Is your feature request related to a problem? Please describe.** We have been (successfully, tysm! ❤️) using cargo about to generate our [licenses.html](https://github.com/apollographql/router/blob/main/licenses.html) file for a while, and we love...

enhancement

**Describe the bug** When using the default HTML output file, even if the input handlebars template has consistent line endings, the output file has a mix of CRLF and LF....

bug

**Describe the bug** I'm behind a corporate proxy, specifically a transparent HTTPS proxy. This means I need to have a CA certificate installed, but I don't need to set any...

bug

If you for example have a `.accepted` configuration for a crate not in the graph, nothing will be outputted, even though it should show a warning that that config entry...

bug

**Is your feature request related to a problem? Please describe.** We compile for several different platforms, each of which uses a different set of targets. Ideally the iOS dependencies wouldn't...

enhancement

**Describe the bug** When using cargo-about, I get a warning 'the definition for X has not been harvested'. It's not clear what this means and what action I should take....

bug

As shown in #227, the current method of requiring license texts to match _exactly_ is maybe a bit too harsh if they only differ by whitespace at the beginning or...

enhancement