About

BuiltforVue is an MIT licensed open source project and completely free to use. BuiltforVue provides a mirror for vue projects available on NPM. It combines information from npm and jsdelivr to provide useful stats to help choose the right package for your project.

Get Involved

Builtforvue is open-source and we still have some work to do. Any contributions, ideas or bug reports are welcome.
Visit our GitHub and help us!
Help Us
If you are a company or an individual and want to help us with the costs involved in development, infrastructure and promotion, you may donate money or anything else you think would be useful. Just send us an email or ask us on GitHub for more details.

Tools Used

How are the scores calculated?

Builtforvue, uses the statistics provided by npms analytics that continuously analyzes the npm ecosystem, gathering as much information as possible from a variety of sources. Using the collected information, a final score for each package is calculated based on four different aspects:
Quality

Quality attributes are easy to calculate because they are self-contained. These are the kind of attributes that a person looks at first when checking out a package.

  • Has README? Has license? Has .gitignore and friends?
  • Is the version stable (> 1.x.x)? Is it deprecated?
  • Has tests? What's their coverage %? Is the build passing?
  • Has outdated dependencies? Do they have vulnerabilities?
  • Has custom website? Has badges?
  • Are there linters configured?

Maintenance

Maintenance attributes allows us to understand if the package is active and healthy or if it is abandoned. These are typically the second kind of attributes that a person looks at when examining a package.

  • Ratio of open issues vs. total issues
  • The time it takes to close issues
  • Most recent commit
  • Commit frequency
  • Release frequency

Popularity

Popularity attributes allows us to understand the package adoption and community size. These are the kind of attributes that a person looks at when they are undecided on the package choice.

  • Number of stars
  • Number of forks
  • Number of subscribers
  • Number of contributors
  • Number of dependents
  • Number of downloads
  • Downloads acceleration

Personalities

If two packages are similar, one tends to choose the one whose author is well known in the community. Relationships between people are also important. When a user follows another, there's a link between them. We can infer that people prefer packages from the users they follow. As of this writing the personalities attributes are not yet implemented.

What does our stack look like?