Initial commit from App

.dockerignore

@@ -0,0 +1,10 @@
+.github
+.vscode
+.git
+.gitignore
+biome.json
+COMMIT_PATTERN.md
+CONTRIBUTING.md
+LICENSE
+README.md
+SECURITY.md

.editorconfig

@@ -0,0 +1,9 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 4
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true

.env.example

@@ -0,0 +1,4 @@
+GIT_USER_EMAIL=your_email
+GIT_USER_NAME=your_name
+HOST=your_host
+PORT=your_port

.github/CODEOWNERS

@@ -0,0 +1,3 @@
+@bush1D3v
+@IsraelPina32
+@eracksonsouza

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,28 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: xd009642
+
+---
+
+**Before raising the issue**
+
+Here are some common things you can try:
+
+* For accuracy of results `--engine llvm` to try the llvm coverage instrumentation if you're on Linux
+* Linker issues `--no-dead-code` dead code linking can cause issues so disable it. This will significantly reduce the accuracy of results with ptrace so you should also use `--engine llvm` if it's not the default on your OS
+
+Check the troubleshooting guide in the repo!
+
+**Describe the bug**
+A clear and concise description of what the bug is and if you're using the ptrace coverage engine (default on x64 Linux) or the llvm instrumentation.
+
+**To Reproduce**
+If possible provide a minimal  example or project where you've observed the issue. Describe how you called tarpaulin and if it seems helpful provide a copy of what tarpaulin printed out to you.
+
+If using ptrace you can use `--dump-traces` to get a log file that can be used for diagnostics. For llvm coverage you can attach the profraw files in `target/tarpaulin/profraws`
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,11 @@
+---
+name: Feature request
+about: request a new feature or a modification or extension of an existing feature
+title: ''
+labels: 'enhancement'
+assignees: xd009642
+
+---
+
+**Describe the feature**
+Give a description of the feature and any information useful to work out if it's a desired feature, already provided by tarpaulin and how it can be implemented. If it could be helpful describe your desired workflow and how this will be utilized in your own projects. If the feature is something like an output report format please include a link to a specification of the format.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,31 @@
+# Pull Request Details
+
+## Motivation and context
+
+<!--- Why is this modification necessary? What problem does it solve? -->
+
+## How is it being tested?
+
+<!--- Please describe in detail how you are testing your modifications. -->
+<!--- Include details of the environment you are testing and the tests you are running to see -->
+<!--- your modifications affect other areas of the code, etc. -->
+
+## Types of modifications
+
+<!--- What types of modifications are included in your code? Place an `x` in all options that apply. -->
+
+- [ ] Dependency update / refactoring / documentation
+- [ ] Bug fix (No modifications that impact backwards compatibility)
+- [ ] New functionality (adaptive or evolutionary) (No modifications that impact backwards compatibility)
+- [ ] Compatibility break (Correction or new functionality that impacts backwards compatibility)
+
+## Check list
+
+<!--- Place an `x` in all applicable options. -->
+<!--- If you have any questions about any of the options, don't hesitate to ask. We're here to help!-->
+
+- [ ] My code complies with the project standard.
+- [ ] My modifications require updating the documentation.
+- [ ] I modified the documentation according to the changes made.
+- [ ] I added tests to cover my modifications.
+- [ ] All new and old tests are passing.

.github/dependabot.yml

@@ -0,0 +1,6 @@
+version: 2
+updates:
+  - package-ecosystem: "npm" 
+    directory: "/" 
+    schedule:
+      interval: "weekly"

.github/workflows/devskim.yml

@@ -0,0 +1,34 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+name: DevSkim
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+  schedule:
+    - cron: '35 6 * * 3'
+
+jobs:
+  lint:
+    name: DevSkim
+    runs-on: ubuntu-20.04
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Run DevSkim scanner
+        uses: microsoft/DevSkim-Action@v1
+
+      - name: Upload DevSkim scan results to GitHub Security tab
+        uses: github/codeql-action/upload-sarif@v3
+        with:
+          sarif_file: devskim-results.sarif

.github/workflows/docker-image.yml

@@ -0,0 +1,64 @@
+name: Docker Package Publish CI
+on:
+  schedule:
+    - cron: '36 20 * * *'
+  push:
+    branches: [ "main" ]
+    tags: [ 'v*.*.*' ]
+  pull_request:
+    branches: [ "main" ]
+
+env:
+  REGISTRY: ghcr.io
+  IMAGE_NAME: ${{ github.repository }}
+  GIT_USER_EMAIL: ${{secrets.GIT_USER_EMAIL}}
+  GIT_USER_NAME: ${{secrets.GIT_USER_NAME}}
+
+jobs:
+  build:
+    runs-on: ubuntu-22.04
+    permissions:
+      contents: read
+      packages: write
+      id-token: write
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+      - name: Install cosign
+        if: github.event_name != 'pull_request'
+        uses: sigstore/cosign-installer@59acb6260d9c0ba8f4a2f9d9b48431a222b68e20 #v3.5.0
+        with:
+          cosign-release: 'v2.2.4'
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@f95db51fddba0c2d1ec667646a06c2ce06100226 # v3.0.0
+      - name: Log into registry ${{ env.REGISTRY }}
+        if: github.event_name != 'pull_request'
+        uses: docker/login-action@343f7c4344506bcbf9b4de18042ae17996df046d # v3.0.0
+        with:
+          registry: ${{ env.REGISTRY }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+      - name: Extract Docker metadata
+        id: meta
+        uses: docker/metadata-action@96383f45573cb7f253c731d3b3ab81c87ef81934 # v5.0.0
+        with:
+          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
+      - name: Build and push Docker image
+        id: build-and-push
+        uses: docker/build-push-action@0565240e2d4ab88bba5387d719585280857ece09 # v5.0.0
+        with:
+          context: .
+          push: ${{ github.event_name != 'pull_request' }}
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+          cache-from: type=gha
+          cache-to: type=gha,mode=max
+      - name: Sign the published Docker image
+        if: ${{ github.event_name != 'pull_request' }}
+        env:
+          TAGS: ${{ steps.meta.outputs.tags }}
+          DIGEST: ${{ steps.build-and-push.outputs.digest }}
+        run: |
+          for i in {1..5}; do
+            echo "${TAGS}" | xargs -I {} cosign sign --yes {}@${DIGEST} && break || sleep 15;
+          done

.gitignore

@@ -0,0 +1,31 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+lerna-debug.log*
+
+node_modules
+.DS_Store
+dist
+dist-ssr
+coverage
+*.local
+
+/cypress/videos/
+/cypress/screenshots/
+
+# Editor directories and files
+.vscode/*
+!.vscode/extensions.json
+.idea
+*.suo
+*.ntvs*
+*.njsproj
+*.sln
+*.sw?
+
+*.tsbuildinfo
+.env

.storybook/main.ts

@@ -0,0 +1,22 @@
+import type {StorybookConfig} from "@storybook/vue3-vite";
+
+const config: StorybookConfig = {
+	stories: ["../src/**/*.stories.ts"],
+	addons: [
+		"@storybook/addon-links",
+		"@storybook/addon-essentials",
+		"@storybook/addon-interactions",
+		"@chromatic-com/storybook",
+	],
+	framework: {
+		name: "@storybook-vue/vue3",
+		options: {
+			docgen: "vue-component-meta",
+		},
+	},
+	docs: {
+		autodocs: "tag",
+	},
+	staticDirs: ["../public"],
+};
+export default config;

.storybook/manager.ts

@@ -0,0 +1,14 @@
+import {addons} from "@storybook/manager-api";
+import {create} from "@storybook/theming";
+
+addons.setConfig({
+	theme: create({
+		base: "dark",
+		textColor: "white",
+		appPreviewBg: "#333333",
+		brandTitle: "NEI Market Analytics",
+		brandUrl: "https://bush1d3v-portfolio.vercel.app/",
+		brandImage: "logo.svg",
+		brandTarget: "_self",
+	}),
+});

.storybook/preview.ts

@@ -0,0 +1,36 @@
+import {themes} from "@storybook/theming";
+import {withActions} from "@storybook/addon-actions/decorator";
+import type {Preview} from "@storybook/vue3";
+import "../src/assets/css/main.css";
+
+const preview: Preview = {
+	parameters: {
+		controls: {
+			matchers: {
+				color: /(background|color)$/i,
+				date: /Date$/i,
+			},
+		},
+		docs: {
+			theme: themes.dark,
+		},
+		layout: "centered",
+		backgrounds: {
+			default: "dark",
+			values: [
+				{
+					name: "dark",
+					value: "#333333",
+				},
+				{
+					name: "light",
+					value: "#eeeeee",
+				},
+			],
+		},
+	},
+	tags: ["autodocs"],
+	decorators: [withActions],
+};
+
+export default preview;

.vscode/extensions.json

@@ -0,0 +1,11 @@
+{
+	"recommendations": [
+		"Vue.volar",
+		"biomejs.biome",
+		"streetsidesoftware.code-spell-checker",
+		"streetsidesoftware.code-spell-checker-portuguese-brazilian",
+		"ms-azuretools.vscode-docker",
+		"Selemondev.shadcn-vue",
+		"EditorConfig.EditorConfig"
+	]
+}

COMMIT_PATTERN.md

@@ -0,0 +1,29 @@
+PT-BR 🇧🇷
+| Categoria | Descrição                                                                                                                                                                                                                                                                                                                             |
+| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| build     | Commits relacionados a ajustes ou melhorias no sistema de construção, como configurações de Webpack, scripts de construção e outros aspectos da infraestrutura de compilação.                                                                                                                                                         |
+| chore     | Commits que envolvem tarefas de manutenção geral no código, mas que não estão diretamente relacionados a funcionalidades específicas ou correções de bugs. Isso pode incluir atualizações de dependências, reorganização de arquivos, formatação de código, melhorias na organização do repositório e outras tarefas administrativas. |
+| ci        | Commits relacionados a configurações ou scripts de integração contínua (CI), como ajustes em configurações do Travis CI, GitHub Actions ou outras ferramentas de CI/CD. Esses commits são importantes para garantir que os testes e a implantação automatizados funcionem corretamente.                                               |
+| docs      | Commits que envolvem a documentação do projeto. Isso pode incluir atualizações em arquivos README, comentários de código, adição ou melhoria de documentação de código-fonte, geração automática de documentação e outras atividades relacionadas à documentação que tornam o projeto mais acessível e compreensível.                 |
+| feat      | Commits que introduzem uma nova funcionalidade no código-fonte. Isso inclui a adição de recursos totalmente novos que melhoram o comportamento ou a capacidade do aplicativo.                                                                                                                                                         |
+| fix       | Commits que corrigem um bug ou problema no código existente. Os commits "fix" são usados para resolver problemas identificados, tornando o aplicativo mais estável e funcional.                                                                                                                                                       |
+| perf      | Commits que visam otimizar o desempenho do código existente, sem adicionar novos recursos. Isso pode incluir melhorias de desempenho em algoritmos, redução de consumo de recursos ou aceleração de operações críticas.                                                                                                               |
+| refactor  | Commits que envolvem refatoração do código, ou seja, alterações no código que não adicionam nem removem funcionalidades, mas melhoram a estrutura, clareza ou eficiência do código. A refatoração é importante para manter o código limpo e fácil de entender.                                                                        |
+| revert    | Commits que revertem alterações anteriores. Eles são usados para desfazer um ou mais commits anteriores que introduziram problemas ou comportamentos indesejados.                                                                                                                                                                     |
+| style     | Commits relacionados a melhorias na formatação do código, como ajustes de espaçamento, formatação de código e outros aspectos visuais. Isso ajuda a manter um estilo de código consistente e legível.                                                                                                                                 |
+| test      | Commits relacionados a testes, como adição de novos testes, correções de testes existentes ou melhorias na infraestrutura de testes. Testes rigorosos são essenciais para garantir que o código funcione corretamente e para evitar regressões.                                                                                       |
+
+ENG 🇺🇸
+| Category | Description                                                                                                                                                                                                                                                                                                                             |
+| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| build     | Commits related to tweaks or improvements to the build system, such as Webpack configurations, build scripts, and other aspects of the build infrastructure.                                                                                                                                                         |
+| chore     | Commits that involve general code maintenance tasks, but are not directly related to specific features or bug fixes. This may include dependency updates, file reorganization, code formatting, repository organization improvements, and other administrative tasks. |
+| ci        | Commits related to continuous integration (CI) configurations or scripts, such as tweaks to Travis CI configurations, GitHub Actions, or other CI/CD tools. These commits are important to ensure that automated testing and deployment work correctly.                                               |
+| docs      | Commits involving project documentation. This may include updates to README files, code comments, adding or improving source code documentation, automatically generating documentation, and other documentation-related activities that make the project more accessible and understandable.                 |
+| feat      | Commits that introduce new functionality into the source code. This includes adding entirely new features that improve the application's behavior or capability.                                                                                                                                                         |
+| fix       | Commits that fix a bug or problem in existing code. "Fix" commits are used to resolve identified issues, making the application more stable and functional.                                                                                                                                                       |
+| perf      | Commits that aim to optimize the performance of existing code, without adding new features. This could include performance improvements in algorithms, reducing resource consumption, or speeding up critical operations.                                                                                                               |
+| refactor  | Commits that involve code refactoring, that is, changes to the code that do not add or remove functionality, but improve the structure, clarity or efficiency of the code. Refactoring is important to keep the code clean and easy to understand.                                                                        |
+| revert    | Commits that revert previous changes. They are used to undo one or more previous commits that introduced problems or unwanted behavior.                                                                                                                                                                     |
+| style     | Commits related to improvements in code formatting, such as spacing adjustments, code formatting and other visual aspects. This helps maintain a consistent and readable code style.                                                                                                                                 |
+| test      | Test-related commits, such as adding new tests, fixing existing tests, or improving the testing infrastructure. Rigorous testing is essential to ensure code works correctly and to avoid regressions.                                                                                       |