## Collection of Ideas so far
* Small packages don't rot necessarily - they can be like honey, so small
packages need special treatment
* a flagging "not working anymore" is needed, with message to author
* parsing of the nimble files would make sense to get an tree of
interdependence betw
So basically parsing all nimble files of all packages. This is a good idea.
Flagging for out of date is a good idea.
This makes sense. But for these kind of packages a "looked over by somebody"\-
label, or anything like this, would make sense, since a newbie don't know what
is stable.
I guess stable packages with few changes are on average smaller packages, I
currently build a analyzer for the package repo an
Yes, you are right. What about the score idea beneath?
## Update: Some bad calculated numbers
I have used the github api and some crude scripts to get an idea of the real
number of packages.
For now no metrics like how old is the project, how many commits at all, how
many stars are applied, but there might be a lot potential for better sorting.
St
## Package-Rot as growth hindrance
Hello! I am new to the community, but I am already in love with the language.
One Problem that I have encountered is that there is "package-rot". Since nim
is a small(adoption wise) language, lots of projects are by a single author and
at some point this autho
