Best practices
Use Store safely by checking product details, licenses, dependencies, team access and account state.
Buying
Before buying, review product details instead of relying on the title alone. Check the description, version, license, price, seller, verification status and dependencies. Prefer published and verified products, especially when the component will be used in a production project.
Selling
Create a merchant account before starting the paid add-product process. Use one repository structure per product and keep names, descriptions, categories and tags clear. Tags should be lowercase and focused so buyers can find the component without guessing unrelated keywords.
Create a new version for code, file, description or tag updates after publication when the current product cannot be edited directly. Update unsafe dependencies before submitting a product again.
Teams and account
Use private products for team-only or client-only components. Keep payment and merchant information up to date, keep CLI tokens and Git access private, and check My finances when payment, payout or subscription actions are blocked.