To highlight the most relevant Meteor packages on Atmosphere, we’ve introduced a public “Verified Accounts” feature to all Meteor Cloud accounts. These accounts, shown with a blue badge on Atmosphere, have been reviewed by our core team and confirmed to be keeping packages up to date and actively addressing issues and PR’s.
Our goal is to keep showcasing packages that are relevant for active community members and make it easier to build and deploy with Meteor.
Want to have your Meteor Cloud account verified? Send us an email at email@example.com with your account name and packages you’d like us to review.
Thank you for continuing to support Meteor Software
Can you add a Verified Listing or Filter by Verified? Otherwise this isn’t getting as much exposure as it deserves.
This is a nice effort to handle software rot that is present.
That said, I’m much more a fan of finding a way to remove atmosphere entirely and building isometric packages from npm packages, let npm be the first class dependancy management tool, let meteor be the first class build tool.
I Support the Idea of listing verified packages with priority.
Purging packages also makes at least sense for all these wrapper packages that did simply wrap npm packages and nothing more. They could all be removed and replaced by their npm counterparts.
However when packages depend on Meteor’s core packages then it won’t be a painless thing to simply move that code to npm. Besides that, who beyond Meteor Users would benefit from these npm packages then?