- Pourquoi Tanzu
- Produits
- Conseil
- Démarrer
- Ressources
- Pourquoi Tanzu
- Produits
- Conseil
- Démarrer
Spring Health Assessment
Our Spring Health Assessment Report helps you understand the health of your Spring dependencies. The generated report will show:
- Whether you have critical security vulnerabilities
- How much effort is required to upgrade all of them to the latest version
- For how long your Spring libraries are covered by open source support
You can then effectively remediate issues with our recommendations, improve your software compliance, and mitigate risk. Try the free Spring Application Health Assessment Report today, and engage with our sales team to learn how VMware Tanzu Spring Runtime or the Spring Consulting team can help.
DémarrerQuestions fréquentes
What information is captured?
We capture only your contact information and the Spring dependencies that are part of your dependency tree. No other open source software (OSS) or private dependencies are included. Broadcom adheres to a strict privacy policy and does not sell or share your personal information, as defined by the California Privacy Rights Act. You can read the details in the VMware Global Privacy Policy. Any use of VMware Offerings is subject to the VMware General Terms.
What is the turnaround time to receive the assessment?
The report is generated real-time as soon as the completed form is submitted. This service is currently in BETA with continuous updates. If the report takes more than 15 minutes to appear, please notify us by sending an email to shar-support.PDL@broadcom.com.
How can I see an equivalent report for my entire portfolio?
We are actively working to provide this capability under Tanzu Spring Runtime. If you are a Tanzu Spring Runtime customer interested in evaluating this feature, please contact your account manager.
What should I do if the generated report is empty?
An empty report may indicate a command failure. Please check the following:
- Ensure you have the `mvnw` or `gradlew` files in the working directory. If your application does not contain these files, use `mvn` or `gradle` instead, but be aware of potential configuration incompatibilities with installed versions.
- Confirm that your `dependencies.txt` file is not empty. If it is, consider checking for potential issues with the file or its contents.
I have a mono repo with several applications. Should I run this at root level or per application?
The commands we are providing support mono repos if they are multi-module projects. You can run the command at the root level of your multi-module project. Otherwise, you need to run the `mvn` or `gradle` commands by folder.
I am getting a parsing error.
This could be because you are using Powershell. At this time, only the Windows zsh shell environment is supported.
1
Starting from your app root, export your dependencies to a .txt file
- Maven
- Maven
- Gradle
- Gradle
./mvnw dependency:tree | grep -E '(org.springframework|io.micrometer)' > spring-dependencies.txt
mvnw.cmd dependency:tree > raw-dependencies.out && findstr /r "org.springframework io.micrometer" raw-dependencies.out > spring-dependencies.txt
echo 'allprojects { task allDeps(type: DependencyReportTask) {}}' > /tmp/dependencies-task.gradle | ./gradlew --init-script /tmp/dependencies-task.gradle -q allDeps | grep -E '(org.springframework|io.micrometer)' > spring-dependencies.txtecho allprojects { task allDeps(type: DependencyReportTask) {}} > %TEMP%/dependencies-task.gradle && gradlew.bat --init-script %TEMP%/dependencies-task.gradle -q allDeps > %TEMP%\raw-dependencies.out && findstr /r "org.springframework io.micrometer" %TEMP%\raw-dependencies.out > spring-dependencies.txt
2