rubyforgood / rubyforgood/alongwithyou
Reconsider `npm audit --audit-level=high` as a hard CI gate
Open
Nobody has claimed this yet.
severity:minor
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 4
- Avg merge
- 9h 34m
- Merged PRs (30d)
- 16
Description
As currently configured, this will block unrelated PRs the day a high advisory lands anywhere in Expo's dependency tree. continue-on-error: true is the alternative tradeoff, worth a deliberate choice either way.
Contributor guide
No contributing guide indexed for this repository
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 CI workflow that runs npm audit --audit-level=high and review how the Expo dependency tree is checked. Compare the current hard gate with continue-on-error: true, then make the selected tradeoff explicit in the workflow and verify that unrelated pull requests behave as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100