Add Moriarty Workflow #36
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GuiGarciaSantos
approved these changes
Sep 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
Hi there! We from the Application Security Squad are rolling out Moriarty.
Feel free to approve and merge this PR if all of the checks are passing successfully.
What is it?
Moriarty is a Clojure SAST developed inside Nubank to analyze and identifies security vulnerabilities and coding errors within the code.
By default it will scan this repository every time a push containing Clojure code is merged to the repository's default branch.
When the scan find a vulnerability it will be made available on the GitHub Security Tab within the repository page.
Changes in this PR
In this PR we're adding the following file under the
.nu/workflowspath:moriarty.yamlContact
If you have any questions or concerns, please reach us out at the
#squad-application-securitySlack channel.