Skip to content

Ran code safety#76

Merged
shilpigoeldev merged 1 commit intomainfrom
feature/code_safety_review
Jan 17, 2025
Merged

Ran code safety#76
shilpigoeldev merged 1 commit intomainfrom
feature/code_safety_review

Conversation

@shilpigoeldev
Copy link
Contributor

What?

I have completed code safety review.

Why?

Peer review is needed to publish a gem.

How?

Ran it via bundle exec rake audit:code interactive=true show_diffs=true reviewed_by=shilpigoeldev

Testing?

No testing needed.

@github-actions
Copy link

🦙 MegaLinter status: ❌ ERROR

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 3 0 0.01s
✅ BASH bash-exec 1 0 0.08s
✅ BASH shellcheck 1 0 0.01s
✅ BASH shfmt 1 0 0.0s
❌ COPYPASTE jscpd yes 1 1.16s
✅ JSON jsonlint 2 0 0.53s
✅ JSON v8r 2 0 3.54s
⚠️ MARKDOWN markdownlint 10 7 0.35s
❌ MARKDOWN markdown-link-check 10 3 8.86s
⚠️ MARKDOWN markdown-table-formatter 10 1 0.42s
✅ REPOSITORY checkov yes no 16.88s
✅ REPOSITORY devskim yes no 1.2s
✅ REPOSITORY dustilock yes no 0.0s
✅ REPOSITORY gitleaks yes no 0.3s
✅ REPOSITORY git_diff yes no 0.01s
✅ REPOSITORY grype yes no 13.38s
❌ REPOSITORY kics yes 2 1.61s
✅ REPOSITORY secretlint yes no 0.71s
✅ REPOSITORY syft yes no 1.63s
✅ REPOSITORY trivy yes no 5.17s
✅ REPOSITORY trivy-sbom yes no 0.11s
✅ REPOSITORY trufflehog yes no 3.07s
❌ SPELL lychee 19 5 1.62s
✅ YAML v8r 6 0 5.34s
✅ YAML yamllint 6 0 0.43s

See detailed report in MegaLinter reports

You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:

MegaLinter is graciously provided by OX Security

@shilpigoeldev shilpigoeldev merged commit 6985140 into main Jan 17, 2025
4 of 6 checks passed
@shilpigoeldev shilpigoeldev deleted the feature/code_safety_review branch January 17, 2025 15:27
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.

2 participants