-
-
Notifications
You must be signed in to change notification settings - Fork 552
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SCTK: resolve npm dependencies based on lockfiles, using a new option #3780
Comments
1 task
AyanSinhaMahapatra
added a commit
that referenced
this issue
Jun 4, 2024
Reference: #3780 Signed-off-by: Ayan Sinha Mahapatra <[email protected]>
AyanSinhaMahapatra
added a commit
that referenced
this issue
Jun 4, 2024
Adds is_direct attribute to differentiate between direct dependecy relationships and dependencies listed in lockfiles which have both direct and transitive dependencies together, which will have is_direct as False. Reference: #3780 Signed-off-by: Ayan Sinha Mahapatra <[email protected]>
AyanSinhaMahapatra
added a commit
that referenced
this issue
Jun 10, 2024
Adds is_direct attribute to differentiate between direct dependecy relationships and dependencies listed in lockfiles which have both direct and transitive dependencies together, which will have is_direct as False. Reference: #3780 Signed-off-by: Ayan Sinha Mahapatra <[email protected]>
6 tasks
AyanSinhaMahapatra
added a commit
that referenced
this issue
Jun 10, 2024
Adds is_direct attribute to differentiate between direct dependecy relationships and dependencies listed in lockfiles which have both direct and transitive dependencies together, which will have is_direct as False. Reference: #3780 Signed-off-by: Ayan Sinha Mahapatra <[email protected]>
@AyanSinhaMahapatra I think this is completed, is it? |
mjherzog
changed the title
ScanCode Toolkit: resolve npm dependencies based on lockfiles, using a new option
SCTK: resolve npm dependencies based on lockfiles, using a new option
Jun 11, 2024
This is done, but not with an option |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: