Skip to main content
Version: v25.07.31

Dependecies Details

The Dependency Details section comprehensively lists libraries alongside their versions and metadata that the backend application depends on. This component is essential in that it could be used by developers, system administrators, and auditors for ensuring compatibility, compliance, and maintainability of the application.

This feature is accessible via the application interface and includes key identifiers such as Item ID, Artifact ID, Group ID, and Version for each dependency.

Accessing Dependency Details​

  • Go to the Login > About > Dependecies Details.

  • The system will display a detailed table containing the ID, Artifact Id, Group Id, and Version for each dependency.

    image-1

Important Notes for Users​

  • This section is read-only and is meant for reference purposes only.
  • Changes to dependencies should be done only by authorized technical teams.
  • Always review dependency versions during:
    • System upgrades
    • Security audits
    • Release version changes
  • Outdated or vulnerable dependencies may impact:
    • System performance
    • Security
    • Application stability
  • If any dependency appears suspicious or outdated, report it to the system administrator or Support team.
  • Ensure dependencies are aligned with approved organizational standards and policies.

FAQs​

Q:1 Why is it important to track dependencies?

Ans: Tracking dependencies is critical for maintaining application stability, ensuring compatibility, and addressing security vulnerabilities in third-party libraries.