I see both sides here.&nbsp; Compromise proposal.<br><br>Include a section in the Project description that lets the developer place links to the supported third-party libraries hosted on external sites.&nbsp; These would be similar to the CVS / Documentation link fields that we have now.
<br><br>Data needed:<br><br>- TItle<br>- Link<br>- Module Release Version(s)<br>- Notes (optional)<br><br>It might also be good to have a function that could check the user&#39;s installed library hash against the &quot;sanctioned&quot; version used by the module developer.&nbsp; This feature would be similar to (incorporated into) the update_status module.&nbsp; The proposed hook would simply be a function that let the module pass hook_hash($path, $filename).&nbsp; We might store the library hash values in the 
<a href="http://module.info">module.info</a> file. If the hash check fails, update_status would flag the module as needeing an update.<br><br>Seem like a plan?<br><br>- Ken Rickard<br>agentrickard<br><br><br>