Why is the version status tag set to "Unresolved"?
Updated: 2024-10-29 MAIA & SBOM Central
There are a number of reasons why the version status cannot resolved for an external artifact, setting it to Unresolved.
First: To be able to be Unresolved, MAIA/SBOMC must be integrated with an external service providing the data, else the status will be No data.
Integration examples:
- The artifact source address is stored in MAIA/SBOMC as Homepage, Vcs, or Alt link. The links may reference a repository hosting service with an API integrated with MAIA/SBOMC.
- Artifact information is found in a external monitoring service having an API integrated with MAIA/SBOMC.
Then, if:
- the artifact version you are using doesn't exist at the repository hosting service, or...
- you have versioning standards ambiguities, for the artifact version a) you are using or/and b) at the repository hosting service, or...
- there is version date ambiguities at the repository hosting service.
the verdict will be Unresolved for the version status.