snaps must have accompanying source available
Metadata
Current evaluation
Maintainer-acknowledged request to persist and publish snap source and build assets for license compliance remains open, with no implementation found.
Suggested action: keep open
Reason: Canonical called this "an agreed goal" in 2017, and later comments identified asset recording and source-snapshot tooling as planned work. It remains unresolved: no source-upload feature or resolving commit was found, while implementation would require coordinated CLI, Store API, persistence, and discoverability work beyond a narrowly specified patch.
Evaluated by: mr-cal-bot
Impact:
74
Quick Win:
7
Complexity:
84
Confidence:
82
Actionability:
57
Issue body
snap packages include open source software. To ensure compliance with licencing and ensure the continued development of this open source users of snaps must be able to download the source code used to create a snap.
Developers must be able (probably required) to upload sources and maybe pointers to .debs used which will persist for the lifetime of the snap.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
74
Quick Win:
7
Complexity:
84
Confidence:
82
Actionability:
57
|
keep open | Maintainer-acknowledged request to persist and publish snap source and build assets for license compliance remains open, with no implementation found. | |
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
2
Complexity:
85
Confidence:
78
Actionability:
28
|
keep open | Long-standing feature request to make source code available/persisted with each snap for GPL compliance. Acknowledged by Canonical as 'an agreed goal' in 2017-2018 but never implemented; still open and unresolved. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
4
Complexity:
60
Confidence:
60
Actionability:
30
|
needs triage | Feature request to require source code availability for snap licensing compliance. No maintainer response, no labels, open for 9+ years. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
12
Staleness:
95
Complexity:
70
Confidence:
60
Support Request:
10
|
close stale | 9-year-old policy proposal requiring snap developers to upload source code for licensing compliance. Zero comments, no labels, no maintainer interaction. Never triaged or acted upon. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | Request to mandate source code availability for snap packages to ensure open-source license compliance. Unaddressed for nearly 9 years with no maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
99
Complexity:
35
Confidence:
95
Support Request:
10
|
close stale | Request to mandate source code availability for snap packages to ensure open-source license compliance. Untriaged, inactive for nearly 8 years, no maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | External contributor requests mandatory source code availability for snap packages to ensure licensing compliance. Issue is completely inactive for nearly 9 years with no maintainer response. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.