ecoAPM / dotnet-libyear

A simple measure of dependency freshness

https://libyear.com

ecoAPM/dotnet-libyear Issues

Support for additional Nuget feeds
Updated 6 months ago3
Crashes when run in a folder with many subfolders with solutions / projects
Closed 6 months ago3
Does not support targeting multiple frameworks with conditions.
Updated 6 months ago1
Wildcard on minor or patch versions of packages are not supported.
Closed 7 months ago2
Use solution files to find projects
Closed 8 months ago6
Update flag isn't actually updating
Closed 2 years ago1
Specify total libyear limit
Closed 2 years ago1
Using preview packages result in negative libyears
Closed 2 years ago2
On error with parsing, would be helpful to know location
Closed 3 years ago1
Quiet mode doesn't output correctly when directory not explicitly declared
Closed 3 years ago1
file locking issues
Closed 3 years ago1
Unexpected exception when package version does not follow semver
Closed 4 years ago4
Handle * as latest version
Closed 4 years ago3
Handle DotNetCliToolReference
Closed 4 years ago2
Update CI Build Target
Closed 4 years ago
ArgumentException when parsing a version
Closed 4 years ago3
PackageReference Update not supported
Closed 5 years ago1
Convert to a global tool
Closed 6 years ago
dotnet new -i: Error: Package "nuget.*.4.0.0.nupkg" is not a valid package specification
Closed 8 years ago2
NullReferenceException
Closed 8 years ago2
Unity 4.0.2 is showing up with negative age
Closed 8 years ago2
Suggestion for a library + cli nuget package split
Closed 8 years ago3
Age needs to sum distinct packages
Closed 8 years ago1
Tool fails with directories with more than one project file
Closed 8 years ago2