Skip to content

too many dependencies from lock files #18

Description

@ret2libc

deplist looks at yarn.lock and package-lock.json files to determine the dependencies of a package. While these dependencies might be used at runtime(or during testing) by the component, they are not "bundled" within the source code base. Usually bundled dependencies in NPM projects are under the ./node_modules directory and they have their own package.json file there, listing the properties of the dependency.

By using yarn.lock and package-lock.json files to determine dependencies without any way to differentiate between bundled dependencies and other types, we can generate too many false positives.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions