`charmcraft analyze` - check for library modifications
Metadata
Current evaluation
Superseded by the charm-libs key. The lint feature for detecting local library modifications was replaced with this configuration approach.
Suggested action: —
No scores available.
Issue body
The way charm libraries generally function means that charm authors end up with local versions of third party libraries, which is by design.
Some people have recently struggled with the contribution/feedback method and made changes to third-party library files *locally*, then had issues that the original library author has struggled to debug/replicate due to disceprancies.
Charmcraft could help solve this by warning in the lint stage if a library has been changed from the original file that was downloaded as part of `charmcraft fetch-lib`.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Superseded by the charm-libs key. The lint feature for detecting local library modifications was replaced with this configuration approach. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
45
Confidence:
85
Support Request:
10
|
needs triage | Feature request to add library modification detection to charmcraft analyze. Untriaged, no labels, last activity over 10 months ago, linked to an internal Jira ticket. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
88
Complexity:
35
Confidence:
75
Support Request:
10
|
needs triage | Feature request to add library modification checks to charmcraft analyze. Open for nearly five years with only a bot comment linking to an internal ticket. Awaiting maintainer assessment and prioritization. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
88
Complexity:
40
Confidence:
85
Support Request:
10
|
needs triage | Proposes lint warning in charmcraft analyze when local libraries differ from fetched originals. Prevents debugging issues from unauthorized modifications. Open, awaiting triage. Jira ticket CRAFT-2773 created. Last activity 304 days ago. |
Update history
| Date | Change |
|---|---|
| closed |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #509 `charmcraft analyze` - check for new version of library | charmcraft | closed | Superseded by issue #417. The feature request to have charmcraft analyze detect newer charm library versions in the store was closed as a duplicate. | |
| #1980 Check for major charm library updates | charmcraft | open | Feature request to detect major (LIBAPI) charm library updates via fetch-libs or a new command, enabling CI workflows to flag breaking library upgrades. Maintainer acknowledged as low priority in June 2025; no implementation yet. |