← Back to issue list

Add `*Craft.yaml` relative path to `Approved` *Craft `response-inspection`

View original Github issue

Metadata

Project
fetch-service
Number
#325
Type
issue
State
open
Author
Vyom-Yadav
Labels
Created
Updated
Closed

Current evaluation

Feature request to add *Craft.yaml relative path to response-inspection output. Acknowledged by maintainer but inactive for 390 days with an unanswered follow-up question.

Suggested action: close stale

Reason: The issue has been inactive for 390 days with no implementation progress. While @cmatsuoka acknowledged the request ('We can add the location of the yaml file relative to the project root'), Vyom-Yadav's follow-up question about the downloads array remains unanswered, and the feature was never implemented. The issue is stale and the feature may have been addressed elsewhere or is no longer relevant.

Impact: 40 Quick Win: 28.0 Staleness: 75 Complexity: 30 Confidence: 60 Support Request: 10

Issue body

### What needs to get done Currently, when *Craft inspection is approved, it only shares that the *craft repository was found: ```json "response-inspection": { "craft.rockcraft": { "opinion": "Unknown", "reason": "git repository does not contain a rockcraft.yaml file" }, "craft.snapcraft": { "opinion": "Approved", "reason": "snapcraft repository found", "annotations": { "checkout": "e684f4cd695f9c9e835dd5d5cbb109d3761753a6" } ``` It would be nice to have the relative path of where this file was found. ### Why it needs to get done This information would help enrich the SBOM with a specifier for the metafile of the package, something like: `PackageDownloadLocation: git+https://git.myproject.org/MyProject@e684f4cd695f9c9e835dd5d5cbb109d3761753a6#/snapcraft/snapcraft.yaml` Doing this on the SBOM Generator side is not feasible as it might not have access to all the repositories, so traversing after cloning is not an option for the sbom generator.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b
Impact: 40
Quick Win: 28.0
Staleness: 75
Complexity: 30
Confidence: 60
Support Request: 10
close stale Feature request to add *Craft.yaml relative path to response-inspection output. Acknowledged by maintainer but inactive for 390 days with an unanswered follow-up question.

Update history

Date Change
created

Related issues

No related issues found above the similarity threshold.