JFrog CLI now supports a `package_alias=true` parameter that eliminates the need to prefix build commands with `jf`. Once set during installation, native package manager commands like `npm install` or `mvn package` are automatically intercepted by JFrog CLI, generating Build-Info metadata for Xray security scanning without any changes to existing CI scripts. A GitHub Actions example demonstrates the setup. Additional benefits include parallel chunked uploads, persistent authentication, and broad package ecosystem coverage across 20+ package types.
Table of contents
Three examples of JFrog CLI requiring script editingRunning native package commands through JFrog CLIExample: How to set up JFrog CLI for GitHub ActionsWhat is JFrog Build-Info, and how does it empower JFrog Xray?What else can JFrog CLI do?How do you get started with JFrog CLI?2.7K Impressions