Analyze the use of badges to show info about the project

[jabalde]

As a developer
I want to show some info in badge format
to show everybody out code quality, last version deployed and other useful info

Technical info

This is an analysis task which is not intended to generate any code. The result of this analysis will be the info we can show and the way to do it. At that moment, some issues will be created to solve the task/s

Acceptance criteria

• Investigate if nodejs developer are showing project related info in badges at README

[jabalde]

The license badge:

[![License: MPL 2.0](https://img.shields.io/badge/License-MPL%202.0-brightgreen.svg)](https://github.com/corunet/openapi-nodejs-cli/blob/main/LICENSE)

[jabalde]

The version deployed at npm registry badge, can be generated using Version Badge but we have to wait for the package to be deployed

A sample badge can be:

For openapi-nodejs-cliwill be something like:

[![@corunet/openapi-nodejs-cli](https://badge.fury.io/js/@corunet/openapi-nodejs-cli)](https://www.npmjs.com/package/@corunet/openapi-nodejs-cli)

[jabalde]

For code quality badge, we can include the project into Codacy but we have to wait for repository to be set as public

A sample bagde can be (this is the mloadgen one:

[![Codacy Badge](https://api.codacy.com/project/badge/Grade/556dc69dff5643ad855a7323c8442876)](https://app.codacy.com/gh/corunet/mloadgen?utm_source=github.com&utm_medium=referral&utm_content=corunet/mloadgen&utm_campaign=Badge_Grade)

[jabalde]

We can start with the three badges commented in this issue:

• license
• last version deployed
• code quality

In the future, we can analyze the need of including more badges