CI/CD Tools - Linting

Open
#9 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
elixir

Research direction

Start by reviewing the CI/CD Tooling training module and the linked OWASP DevSecOps linting guidance and security article. Compare the module's current linting coverage with the proposed security and SAST topics; done would require a decided scope and corresponding training content, but the issue does not identify files or tests.

Written by the indexing model from the issue text.

Description

discussion new content non-elixir content

Linting, code patterns, security anti-patterns, SAST all run in similar circles - I believe there is some things you could implement in your linting practices that could have an effect on code security.

What that is exactly is still to be determined, but I'd love to start collecting thoughts on it and if should be included in the training module for CI/CD Tooling.

For the Elixir specific examples, it would most likely be referencing Credo.

Relevant Resources:

Dominant language
Elixir
Stars
732
Forks
172
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from erlef/elixir-secure-coding

All issues in erlef/elixir-secure-coding

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.