Identified NOASSERTION not contained in the result from the backed

[fviernau]

Problem

1. When a file contains a single finding with NOASSERTION as the license.
2. And the snipped is identified by a matching include rule
3. Then the result contains an entry for the file with licenses = []
4. Problem: The NOASSERTION disappears from the result but may be relevant

Proposal

• Include also NOASSERTION in the result.

Question

As a work around or alternative, would it be valid to interpret licenses = [] as NOASSERTION ?

[isasmendiagus]

Thanks for the report — trying to reproduce on our side and need a bit more context:

• What are you scanning — a source file or a .wfp fingerprint? If you can share the file (or the WFP) that triggers it, that'd help a lot.
• The scanoss.json settings you're using (the relevant include rule).
• The resulting result.json entry for that file.

For context on what we're seeing so far: when a snippet matches a component that has no license in the KB, the server returns licenses: [] — we haven't observed it ever return the literal string NOASSERTION. So we want to confirm whether your case is (a) the server returning [] for a no-license component, or (b) a specific component whose declared license is actually NOASSERTION and it's getting dropped. Your file/purl would tell us which.