[Feature]: Add support for restricting dependency downloads to a list of allowed registries/URLs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.1k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
- I'd be willing to implement this feature (contributing guide)
- This feature is important to have in this repository; a contrib plugin wouldn't do
Describe the user story
As a result of the many recent supply chain attacks, I'm looking for a way to prevent yarn from installing dependencies from any registry or location other than a specific list of allowed resources.
Describe the solution you'd like
For instance, maybe a configuration like the following
allowedDependenciesUrls
- registry.npmjs.org/*
- my-private-registry.com/*
- some-mirror.edu/*
And with a default value of the following if not set
allowedDependenciesUrls
- registry.npmjs.org/*
If a sub-dependency of https://my-secure-registry-bucket.s3.amazonaws.com/evil/some-dep-1.2.3.tgz were requested, the install would fail.
Describe the drawbacks of your solution
I'm not familiar with the how package managers are actually built but I think
- There could be overlapping concerns with such a setting and other yarn settings like
approvedGitRepositoriesandenableHardenedMode - I would think in the future there may be some dependency standards group that would define a consistent way for npm, yarn, pnpm, bun, etc. to all do this in the same way and this might have to then be updated later
Describe alternatives you've considered
- Using
approvedGitRepositories- but my understanding is that this setting does cover non-git URLs like malicious s3 buckets - Switch to another package manager
Other Notes
I haven't contributed to yarn before but I'm open to doing so. I didn't see the same request already so hopefully this issue isn't already covered somewhere else (apologies if it is.)
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
The issue does not name files or tests. Start by tracing how Yarn resolves and downloads dependency URLs, then compare the proposed allowlist with approvedGitRepositories and enableHardenedMode. Done means installs reject dependencies from resources outside the configured list, including transitive dependencies, while the default behavior is defined and tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- security, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100