dotnet libyear

We have hosted the application dotnet libyear in order to run this application in our online workstations with Wine or directly.

Quick description about dotnet libyear:

A simple measure of software dependency freshness. It is a single number telling you how up-to-date your dependencies are. Rails 5.0.0 (June 30, 2016) is roughly 1 libyear behind 5.1.2 (June 26, 2017). There are obviously more nuanced ways to calculate dependency freshness. The advantage of this approach is its simplicity. You will be able to explain this calculation to your colleagues in about 30s. If your system has two dependencies, the first one year old, the second three, then your system is four libyears out-of-date. At Singlebrook we try to keep our client�s apps below 10 libyears. We regularly rescue projects that are over 100 libyears behind. "lib" is short for "library", the most common form of dependency. The --versions flag provides a metric for an installed dependency�s freshness relative to the newest release�s major, minor, and patch versions. Of course, this is most useful for dependencies that follow a consistent versioning scheme such as semver.

Features:

• A simple measure of dependency freshness
• Zero or more directories or csproj files may be passed
• If no arguments are passed, the current directory is searched
• If no csproj is found in a directory, subdirectories are searched
• Only show outdated packages
• Update project files after displaying packages

Programming Language: C#.
Categories: