Reconsider `npm audit --audit-level=high` as a hard CI gate

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, typescript
Domain
ci-cd, security

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.

Description

severity:minor

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.

Dominant language
TypeScript
Stars
9
Forks
4
Avg merge
9h 34m
Merged PRs (30d)
16

Contributor guide

No contributing guide indexed for this repository

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 rubyforgood/alongwithyou

All issues in rubyforgood/alongwithyou

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.