Build Report -

Environment
Java Version Loading...
Vendor Version Loading...
Graal Compiler Optimization level: Loading..., Target machine: Loading..., PGO: Loading...
C Compiler Loading...
Garbage Collector Loading...

Analysis Results
Category Types in % Fields in % Methods in %
Reachable Loading... Loading... Loading... Loading... Loading... Loading...
Reflection Loading... Loading... Loading... Loading... Loading... Loading...
JNI Loading... Loading... Loading... Loading... Loading... Loading...
Loaded Loading... 100.000% Loading... 100.000% Loading... 100.000%
 
Loading...

Security Report
Loading...
Loading...
Loading...
Loading...

Resource Usage
Total build time
Garbage collection
Peak RSS
CPU load

Method-based code area breakdown

The chart below shows how different packages relate to each other depending on the selected breakdown type.

Note: A fixed threshold (0.1% of total percentage relative to current root package) is used to limit the amount of data shown on the chart.
Represents different breakdown types. Each type is represented by a specific method set and a metric by which the package percentages are calculated.
 
Loading...

Packages and classes
Name ... in total
Object types Count Size... in total
Module
  • Shows the resource module
  • Entries marked as unnamed are not from module
 Name
  • Shows the resource name
  • Number in the brackets represents number of different resources with same name and module values
 Count
  • Shows the number of occurrences for the particular resource.
  • A number greater than one can indicate a problem, because it means that a resource was embedded multiple times
 Origin
  • Shows the resource location on the system
  • Entries marked as Injected were added programmatically
  • Browsers cannot open all types of resources (e.g. jars)
 Type
  • Shows the resource type
    • : directory resource
    • : file resource
    • : missing resource - was tried to be registered but does not exist on the system
 Size
  • Shows the resource size
  • The size of directory resources depends on the size of all directory entry names

Components
Organization Artifact Version

Unassociated Types

These types (such as classes, interfaces, or annotations) cannot be linked to an SBOM component. If these types contain vulnerabilities, they may not be detected during SBOM scanning.
To fix this, ensure that proper GAV coordinates (Group ID, Artifact ID, and Version) are defined in the project POM's properties or in MANIFEST.MF using standard formats.
Name