Important Package

There may be some package(s) that are more important than other at your organisation.

Some examples of reasons you may categorise a package as important:

• "this library is critical to the operation of our production services" i.e. the version of Application Performance Monitoring (APM) libraries
• "this tool underpins the boilerplate generation that we use to power our Go services" i.e. the version of oapi-codegen, ogen
• "this framework is used to provide a batteries-included set of tooling to building web services" i.e. the version of Spring Boot or Next.JS
• "this library is used to power inter-service gRPC communication, which we don't want to have too out-of-date" i.e. a package called github.com/$org/grpc-models-go

Using Important Packages provides a means to elevate certain dependencies up above others, allowing for a simpler means of querying them.

Important Packages build on top of Package Aliases to provide a means to provide a straightforward many-to-one mapping.