openrewrite / openrewrite/rewrite-github-actions
Add `lockfile-lint` to `npm/yarn` projects to validate the package-lock files
Open
Nobody has claimed this yet.
recipe
- Dominant language
- Java
- Stars
- 1
- Forks
- 9
- Avg merge
- 5h 27m
- Merged PRs (30d)
- 12
Description
Read more : https://www.npmjs.com/package/lockfile-lint
Example
jobs:
check-dist:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Set Node.js 16.x
uses: actions/setup-node@v2.4.1
with:
node-version: 16.x
- name: Validate package-lock
run: npx lockfile-lint --path package-lock.json --allowed-hosts npm yarn --validate-https
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the repository's existing npm/yarn and GitHub Actions recipe entry points, then compare how they identify package-lock.json files. Use the issue's npx lockfile-lint command as the validation reference; done means the recipe applies the requested lockfile checks for npm/yarn projects and has coverage for the supported cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100