HolyLab / HolyLab/HolyLabRegistry
Dependency confusion
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 17
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
@GunnarFarneback added new functionality to protect registries against a malicious attack via "dependency confusion". See details in https://github.com/JuliaRegistries/RegistryCI.jl/pull/348. This registry has now been protected thanks to https://github.com/JuliaRegistries/General/pull/30175. I have not yet taken the time to dig into this issue in detail, but we should check whether we need to reciprocate: do we need to make sure that General is protected against dependency confusion from this registry?
Since it's a potential security hole, this is a high-priority issue and should be tackled ASAP. @kdw503, can you take this on?
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
No files or tests are named. Start by reviewing RegistryCI.jl PR #348 and General PR #30175, then compare their dependency-confusion protections with this registry's setup. Done means determining whether reciprocal protection is required and documenting or implementing the resulting scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100