CycloneDX/cyclonedx-node-yarn

option to not interact with installed project(cache/fs)

Closed

#49 opened on Mar 26, 2024

View on GitHubContributor guide
 (4 comments) (0 reactions) (1 assignee)JavaScript (10 forks)auto 404
enhancementhacktoberfesthelp wanted

Repository metrics

Stars
 (27 stars)
PR merge metrics
 (PR metrics pending)

Description

current implementation requires a fully setup env.

yarn runs under the hood an install, if the setup is not complete. This is a yarn-internal process.

what about analysis of a not-installed setup in a no-network environment?

lets have a CLI switch --package-lock-only, that causes no interaction with the cache/fs

Contributor guide

Research direction
Examine the CLI argument parsing and the function that triggers yarn install. Locate where the package lock is read, then add a ` package lock only` flag to bypass installation and use the existing lockfile for analysis.
Tech stack
javascriptnodejs
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.jsYarn
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70