a little suggestion

[vinnie]

Creating a list of package in repository ordered by date (also a function in appbrowser is good).
This is not much for users but for maintainers.
Installation of dependecies is not recursively and if you change a package is better to know easily.

[alu]

i think, there is a mention of dates in the info file of the extension which tell you when the extension has been built, change/updated, but maybe i do not get your point correctly

[bmarkus]

Date in the info file is just informative, can't be used for such purpose.

[Lee]

If appbrowser could display the extensions from most recently updated to least recently updated (with dates or version visible in the list), one would know immediately if he needed to update his favorite apps.

Deps might still slip by unnoticed, of course, if one is not careful.

[roberts]

I find it easier to find apps when in alphabetic order.
I will offer some new options in appsaudit, check for updates, and refresh your deps, as well, use existing dep for dependency database used in the report options..

[roberts]

You can always run upgrade_tce.sh to keep you extensions upgraded.

[vinnie]

Using the date of last modified file? (not use the date in the info, which always remains at the discretion of the maintainer)
   
I suggested the appbrowser but could also be a mailing list for updates, or simply a dynamic table on the web.

Example to explain my point of view:
1-Manteiner creating 3 packages with 15 total dependecies.
2-One or more of these dependencies are updated.
3-A mailing list inform automaticly a members of changed (or a feed, or a order in appbrowser, or table in web page).