Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Snyk Vulnerabilities #22

Merged
merged 3 commits into from
Mar 28, 2024

Conversation

OS-ricardomoreirasilva
Copy link
Contributor

@OS-ricardomoreirasilva OS-ricardomoreirasilva commented Mar 28, 2024

  • Add Gemfile.lock file to the gitignore file as this is generating a Snyk medium-level severity.
  • Move LICENSE to root, as mentioned here.
  • Remove unused files.

Add `Gemfile.lock` file to the `gitignore` file as this is generating a Snyk medium-level severity.
These were part of the default `README` file, which has been changed in the meantime.
@hectorjdgdev hectorjdgdev force-pushed the chore/fix-snyk-vulnerabilities branch from fc21734 to 8a595c4 Compare March 28, 2024 12:50
Copy link

sonarcloud bot commented Mar 28, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@OS-ricardomoreirasilva OS-ricardomoreirasilva marked this pull request as ready for review March 28, 2024 12:57
@OS-ricardomoreirasilva OS-ricardomoreirasilva requested a review from a team as a code owner March 28, 2024 12:57
@OS-ricardomoreirasilva OS-ricardomoreirasilva changed the title Chore/fix snyk vulnerabilities Fix Snyk Vulnerabilities Mar 28, 2024
@OS-ricardomoreirasilva OS-ricardomoreirasilva merged commit e21bb03 into development Mar 28, 2024
7 checks passed
@OS-ricardomoreirasilva OS-ricardomoreirasilva deleted the chore/fix-snyk-vulnerabilities branch March 28, 2024 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants