dotnet-libyear icon indicating copy to clipboard operation
dotnet-libyear copied to clipboard

A simple measure of dependency freshness

Results 4 dotnet-libyear issues
Sort by recently updated
recently updated
newest added

**Steps to reproduce** 1. Create a project. 2. Add a package. 3. Modify the project to support multiple frameworks `net6.0;net7.0;net8.0` 4. Modify the project so that it uses different packages...

bug
large

At the moment this project only supports output to a table. While fantastic for human readability, it leads something to be desired when it comes to machine readability. Use: -...

## Story As a engineer who utilises private feeds, I want to be able to scan internal packages, so that I am also conscious of drift from internal standards. ##...

feature
large

**Steps to reproduce** 1. create a project with an outdated dependency 2. run `dotnet libyear -u` on that project **Expected behavior** - the project file is updated - running `dotnet...

bug