← Back to issue list

Improve inspector license extraction

View original Github issue

Metadata

Project
fetch-service
Number
#373
Type
issue
State
open
Author
cmatsuoka
Labels
Created
Updated
Closed

Current evaluation

Feature request to improve license identifier extraction in Fetch Service to prevent SPDX degradation, false positives, and normalize names. Untriaged, 390 days since last activity.

Suggested action: needs triage

Reason: The issue has no labels, no assignee, and no maintainer response beyond the author's own comment. Despite being authored by a maintainer (cmatsuoka), it hasn't been formally triaged or prioritized. The referenced issue fetch-service#323 is still open and tracks related SPDX compliance work.

Impact: 60 Quick Win: 27.0 Staleness: 75 Complexity: 55 Confidence: 65 Support Request: 5

Issue body

### What needs to get done The license identifier provided by the Fetch Service can be improved in different ways to prevent problems to metadata consumers: - Mitigate [degradation of valid SPDX licenses](https://bugs.launchpad.net/ubuntu/+source/licensecheck/+bug/2104867) - Prevent false positives - Normalize license names ### Why it needs to get done Degraded license names make it impossible for consumers to recover the original artifact license because information is lost. False positives can result in inaccurate SBOM information. Normalized names cause minimal disruption to consumers if the license extracting implementation is modified or replaced in the Fetch Service.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b
Impact: 60
Quick Win: 27.0
Staleness: 75
Complexity: 55
Confidence: 65
Support Request: 5
needs triage Feature request to improve license identifier extraction in Fetch Service to prevent SPDX degradation, false positives, and normalize names. Untriaged, 390 days since last activity.

Update history

Date Change
created

Related work

  • Related To: fetch-service#323 (confidence 85%)

    The issue body explicitly references #323 ('Non SPDX compliant license expressions') and the author notes this may solve it. Both track license normalization work in the Fetch Service.

Related issues

No related issues found above the similarity threshold.