Run Packmind (ex-Promyze) CLI to detect best coding practices in the source code
npm install packmind-cliCheck full doc here: https://docs.packmind.com/detect-practices-in-your-code/packmind-cli/run-with-npm
--url option to override Packmind URL, if it differents than the one encoded in the API Key"/src/", "/.js", "/pom.xml").xml files in the list of supported file extensions for analysis.node 20.18.+--snapshot option to send analysis report to Packmind (experimental)axios* Add --log option which can be either info or debug(default: info).
* Improve execution performance for the onlyChanged mode
* Add xcode formatter.
* Improve UI of console formatters
* Minor fix on the onlyChanged mode
* Update default settings batchSize to 20 and batchConcurrent to 4.
* Adjust main entrypoint so that it does not conflict with previous promyze-cli, that needed to be removed before installing packmind-cli. This is no longer required.
* Better error handling from server side. If any part of the analysis failed, it does not fail silently anymore. The execution stops and the error is shown in the console.
* Add gitlabMR option to restrict the scope of analysis within Gitlab Merge Requests to only the files that have been modified in the MR. This requires a PACKMIND_GITLAB_TOKEN to be set in environment variable to fetch Gitlab API in read-only.
* Add batchSize and batchConcurrent to tune runtime performance. Usage is intended for large codebases and self-hosted customers.
* Fix runtime issue
* Add more logging
* Optimize space filtering to avoid unnecessary API calls
* Improve SonarQube reporting
* Add --spaces option to filter results based on spaces from which practices belong to
* Remove url option as apiKey is enough
* Add --ruleIdSarif option to indicate what should be the ``ruleId` property in the SARIF reports. praticeId
* Can be either (immutable) or practiceName` (mutable)