Skip to content

(Scanner) implement dependency-confusion warning #492

@fraxken

Description

@fraxken

The idea is to implement a warning when there is risk of dependency confusion: https://medium.com/@alex.birsan/dependency-confusion-4a5d60fec610

Scenarios:

  • The dependency declared in the package.json do not exist on the public NPM registry (it's probably hosted privately somewhere).
  • The dependency is identified from a custom registry with a namespace (and resolved if local configuration is ok) but there no public organization exists on NPM.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions