-
Notifications
You must be signed in to change notification settings - Fork 499
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
✨ Adds Elixir and Gleam as languages #4408
Conversation
6b616cf
to
544bb3a
Compare
544bb3a
to
f2548b4
Compare
Signed-off-by: Kiko Fernandez-Reyes <[email protected]>
Signed-off-by: Kiko Fernandez-Reyes <[email protected]>
f2548b4
to
2c39826
Compare
Co-authored-by: Bram Verburg <[email protected]> Signed-off-by: Kiko Fernandez-Reyes <[email protected]>
Thanks for catching the issues in Elixir and Gleam. I have also corrected the bug for the Erlang commit and added it here, unless you prefer a specific PR for the Erlang broken test. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution and quick responses! Please fix DCO and I can get this merged.
https://github.com/ossf/scorecard/pull/4408/checks?check_run_id=33054586665
Signed-off-by: Kiko Fernandez-Reyes <[email protected]>
57c3e51
to
8cf916e
Compare
I have fixup (squash) some commits together and re-add the forgotten |
@spencerschrock Thanks again for your fast response rate! Thanks again! |
No worries, family comes first :) |
What kind of change does this PR introduce?
Use the presence of property-based tests to detect the use of fuzzing in Elixir and Gleam code.
What is the current behavior?
There is no support for fuzz detection for Elixir and Gleam.
What is the new behavior (if this is a feature change)?**
Adds Elixir and Erlang as a client language.
Scans for the import of property-based test frameworks to detect the use of fuzzing in Elixir and Gleam
Which issue(s) this PR fixes
NONE
Special notes for your reviewer
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)