
Research
Malicious npm Packages Impersonate Flashbots SDKs, Targeting Ethereum Wallet Credentials
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Checks playbooks for practices and behavior that could potentially be improved
ansible-lint
checks playbooks for practices and behavior that could
potentially be improved. As a community-backed project ansible-lint supports
only the last two major versions of Ansible.
Visit the Ansible Lint docs site
This action allows you to run ansible-lint
on your codebase without having to
install it yourself.
# .github/workflows/ansible-lint.yml
name: ansible-lint
on:
pull_request:
branches: ["main", "stable", "release/v*"]
jobs:
build:
name: Ansible Lint # Naming the build is important to use it as a status check
runs-on: ubuntu-24.04
steps:
- uses: actions/checkout@v4
- name: Run ansible-lint
uses: ansible/ansible-lint@main # or vX.X.X version
# optional (see below):
with:
args: ""
gh_action_ref: "<version - e.g. `v25.5.0`>" # Not recommended for non-composite action use
setup_python: "true"
working_directory: ""
requirements_file: ""
By default, the workflow uses ansible-lint installed from main
. For production or stable workflows, it is recommended to specify a particular release tag (in format v.X.X.X).
All the arguments are optional:
args
: Arguments to be passed to ansible-lint command.gh_action_ref
: The git branch, tag, or commit to use for ansible-lint.
Not recommended for standard use - only use with composite actions where
GH_ACTION_REF
is set to the parent action version.requirements_file
: Path to the requirements.yml file to install role and
collection dependencies.setup_python
: If python should be installed. Default is true
.working_directory
: The directory where to run ansible-lint from. Default is
github.workspace
. Needed if you want to lint only a subset of
your repository.For more details, see ansible-lint-action.
Refer to the Talk to us section of the Contributing guide to find out how to get in touch with us.
You can also find more information in the Ansible communication guide.
Please read Contribution guidelines if you wish to contribute.
Please see the Ansible Community Code of Conduct.
The ansible-lint project is distributed as GPLv3 due to use of GPLv3 runtime
dependencies, like ansible
and yamllint
.
For historical reasons, its own code-base remains licensed under a more liberal MIT license and any contributions made are accepted as being made under original MIT license.
ansible-lint was created by Will Thames and is now maintained as part of the Ansible by Red Hat project.
FAQs
Checks playbooks for practices and behavior that could potentially be improved
We found that ansible-lint demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.