yarnpkg/yarn

Yarn audit does not work with an external repository

Open

#7012 opened on Feb 7, 2019

View on GitHub
 (11 comments) (14 reactions) (0 assignees)JavaScript (41,514 stars) (2,731 forks)batch import
good first issuehelp wanted

Description

Do you want to request a feature or report a bug? Bug

What is the current behavior?

When running yarn audit with the --registry flag, it uses the main yarn repo anyway.

If the current behavior is a bug, please provide the steps to reproduce.

Execute yarn audit --registry https://registry.npmjs.org/

What is the expected behavior?

Audit calls are made to the defined registry. This is especially important for everyone with third party repo's where the outside world it blocked on CI agents. Or if you're using some kind of proxy.

Please mention your node.js, yarn and operating system version.

Mac Os Mojave Yarn 1.13.0 Node 10.15.1

Contributor guide

Tech stack
javascriptnodejs
Domain
cli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with Yarn CLIBasic Node.jsUnderstanding of package registries
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate how the ` registry` flag is handled in the audit command. Look at the source code in `src/cli/commands/audit.js` to see where the registry URL is used. Check if there is a fallback to the default registry. Review existing tests for audit with custom registries and consider adding a test that verifies the API call URL when ` registry` is passed.