OpenConext / OpenConext/Stepup-Gateway
Implement potential NPM vulnerability mitigations
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 6
- Forks
- 3
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 10
Description
Based on the recent supply chain attacks, we should harden our usage of yarn to prevent leaking of credentials on devmachines or pipeline runners.
https://trigger.dev/blog/shai-hulud-postmortem
If possible:
- Configure yarn to only use packages x days old.
- Configure yarn to not allow packages to execute scripts, unless explicitly allowed on a package level
If not possible, switch package manager? :)
Projects to implement:
- Stepup-Gateway
- Stepup-selfservice
- Stepup-ra?
- Engineblock
- sp-dashboard
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 Yarn configuration and dependency setup in Stepup-Gateway, Stepup-selfservice, Stepup-ra, Engineblock, and sp-dashboard. Check whether the requested package-age and install-script controls are supported, then define consistent mitigation or package-manager decisions for each project. Done means all applicable projects have the agreed safeguards or a documented alternative.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, ci-cd, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100