Skip to content
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

fix(nodejs): add name validation for package name from package.json #6268

Merged

Conversation

DmitriyLewen
Copy link
Contributor

Description

Npm uses some rules for package names - https://docs.npmjs.com/cli/v10/configuring-npm/package-json
We need to reproduce npm logic and return error for invalid package names.

Related Discussions

Checklist

  • I've read the guidelines for contributing to this repository.
  • I've followed the conventions in the PR title.
  • I've added tests that prove my fix is effective or that my feature works.
  • I've updated the documentation with the relevant information (if needed).
  • I've added usage information (if the PR introduces new options)
  • I've included a "before" and "after" example to the description (if the PR is a user interface change).

@DmitriyLewen DmitriyLewen self-assigned this Mar 5, 2024
@DmitriyLewen DmitriyLewen marked this pull request as ready for review March 5, 2024 08:22
@@ -40,6 +43,10 @@ func (p *Parser) Parse(r io.Reader) (Package, error) {
return Package{}, xerrors.Errorf("JSON decode error: %w", err)
}

if !IsValidName(pkgJSON.Name) {
return Package{}, xerrors.Errorf("Name can only contain URL-friendly characters")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the warning message is enough. Otherwise, if a package.json file contains an invalid name for testing, it fails the whole scanning.

Copy link
Collaborator

@knqyf263 knqyf263 Mar 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or is it anyway converted into a warning in analyzer.go? If so, never mind my comment.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or is it anyway converted into a warning in analyzer.go

Right.

@knqyf263 knqyf263 added this pull request to the merge queue Mar 11, 2024
Merged via the queue into aquasecurity:main with commit 12c5bf0 Mar 11, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants