Skip to content

Move package updaters from Frogbot into jfrog-cli-security#775

Open
orto17 wants to merge 8 commits into
jfrog:devfrom
orto17:move-package-updaters
Open

Move package updaters from Frogbot into jfrog-cli-security#775
orto17 wants to merge 8 commits into
jfrog:devfrom
orto17:move-package-updaters

Conversation

@orto17

@orto17 orto17 commented Jun 14, 2026

Copy link
Copy Markdown
Contributor

Relocates the package updater implementations (Go, Maven, Npm, Pnpm, Pip/Poetry/Pipenv) from the Frogbot repository into utils/remediation/packageupdaters/ so they can be shared by both Frogbot and the auto-fix action. Introduces a lean FixDetails struct and a GetCompatiblePackageUpdater factory. Removes unsupported technologies (Yarn, Gradle, Nuget, Conan). Moves test files and testdata alongside the implementation.

  • The pull request is targeting the dev branch.
  • The code has been validated to compile successfully by running go vet ./....
  • The code has been formatted properly using go fmt ./....
  • All static analysis checks passed.
  • All tests have passed. If this feature is not already covered by the tests, new tests have been added.
  • Updated the Contributing page / ReadMe page / CI Workflow files if needed.
  • All changes are detailed at the description. if not already covered at JFrog Documentation, new documentation have been added.

Relocates the package updater implementations (Go, Maven, Npm, Pnpm, Pip/Poetry/Pipenv)
from the Frogbot repository into utils/remediation/packageupdaters/ so they can be shared
by both Frogbot and the auto-fix action. Introduces a lean FixDetails struct and a
GetCompatiblePackageUpdater factory. Removes unsupported technologies (Yarn, Gradle, Nuget,
Conan). Moves test files and testdata alongside the implementation.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@orto17 orto17 changed the base branch from main to dev June 14, 2026 07:36
- Add techutils.Poetry and techutils.Pipenv to GetCompatiblePackageUpdater
  (both route to PythonPackageUpdater, which already handles them internally)
- Add them to SupportedFixTechnologies for consistency
- Add TestGetCompatiblePackageUpdater covering all supported and unsupported techs
- Run go mod tidy to promote gjson/sjson from indirect to direct requires

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@orto17 orto17 added the safe to test Approve running integration tests on a pull request label Jun 14, 2026
@github-actions github-actions Bot removed the safe to test Approve running integration tests on a pull request label Jun 14, 2026
}
}

func TestGetAllDescriptorFilesFullPaths(t *testing.T) {

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I notice that it fails in the unit tests?

@attiasas attiasas left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Nice job, I would just move some of the files to different location for this repository

  1. testdata should be under tests/testdata, prefer to use currently avaliable projects if you can. add if missing under the right location
  2. I would put utils/remediation in sca/remediation or even remediation/sca from root (in case we will expend to remediate JAS as well)

@attiasas attiasas added ignore for release Automatically generated release notes safe to test Approve running integration tests on a pull request labels Jun 15, 2026
@github-actions github-actions Bot removed the safe to test Approve running integration tests on a pull request label Jun 15, 2026
- utils/remediation/packageupdaters/ -> remediation/sca/packageupdaters/
- utils/remediation/testdata/ -> tests/testdata/projects/remediation/
- Update testdata relative paths in test files
- Fix TestGetAllDescriptorFilesFullPaths expected results to include multi1/pom.xml
@orto17 orto17 added the safe to test Approve running integration tests on a pull request label Jun 15, 2026
@github-actions github-actions Bot removed the safe to test Approve running integration tests on a pull request label Jun 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ignore for release Automatically generated release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants