title: NuGet official package source: Should I be worried about the safety of the packages?
body: <p>According to <a href="http://haacked.com/archive/2010/10/06/introducing-nupack-package-manager.aspx" rel="noreferrer">this page</a>:</p>
  
  <blockquote>
    <p>No central approval process for adding packages. When you upload a package to the NuGet Package Gallery (which doesn’t exist yet), you won’t have to wait around for days or weeks waiting for someone to review it and approve it. Instead, we’ll rely on the community to moderate and police itself when it comes to the feed. This is in the spirit of how CodePlex.com and RubyGems.org work. </p>
  </blockquote>
  
  <p>This makes me feel uneasy. Before I download a Firefox add-on, I know it should not contain malicious code, because AFAIK all add-ons on addons.mozilla.org are reviewed by Mozilla. Before I download a open source project from codeplex.com or code.google.com, I know it should be safe because anyone can check it's source code. And I can also use WOT (web of trust) to check how other people think about the project.</p>
  
  <p>But before I download a package from NuGet official package source. Take <a href="http://nuget.org/Packages/Packages/Details/CommonServiceLocator-1-0" rel="noreferrer">this one</a> for example. I do no know who made this package, nor what is contained in the package. It seems to me that anyone can pack anything into a package, give it any name they want (like "Microsoft Prism", as long as the name is not taken), then upload it to the official package source.</p>
  
  <p>Should I be worried about the safety of the packages on NuGet official package source?</p>