Allow `charmcraft status anycharm` for everyone
Metadata
Current evaluation
Anonymous charmcraft status remains unavailable to non-publishers; the request is unresolved and under discussion after a maintainer raised public-data and API scope questions.
Suggested action: keep open
Reason: Keep open: maintainer lengau acknowledged the request but noted that the current endpoint exposes publisher-only active branches and suggested the consumer API; taurus-forever responded with concrete juju info usability limitations. The issue remains open with internal ticket CRAFT-2804, and the current implementation still uses the authenticated list_releases path, with no resolving commit or PR cited.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
48
Quick Win:
12
Complexity:
59
Confidence:
84
Actionability:
62
|
keep open | Anonymous charmcraft status remains unavailable to non-publishers; the request is unresolved and under discussion after a maintainer raised public-data and API scope questions. | |
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
22
Complexity:
20
Confidence:
85
Actionability:
70
|
keep open | Feature request to allow anonymous read access for `charmcraft status`, which currently requires publisher/collaborator permissions. Open for ~2.5 years with no implementation. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
16
Staleness:
75
Complexity:
60
Confidence:
70
Support Request:
20
|
needs triage | Feature request to allow anonymous read access to `charmcraft status` so non-publishers can view channel/release info. A maintainer questioned the value over `juju info`; reporter pushed back. No labels, no further activity since Apr 2024. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
30
Confidence:
80
Support Request:
15
|
close stale | Request to allow public read access to charmcraft status for non-maintainers, improving usability over juju info. Currently open with no maintainer follow-up for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
15
Confidence:
80
Support Request:
10
|
close stale | Request to make charmcraft status anycharm publicly readable for better usability compared to juju info. Open since ~2 years, maintainer asked clarifying questions ~10 months ago with no follow-up. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
25
Confidence:
60
Support Request:
10
|
needs triage | Request to allow anonymous read access for charmcraft status anycharm. Currently restricted to maintainers. Open since 2022, last activity 10 months ago after maintainer asked for clarification on differences from juju info. |
Update history
No update history recorded yet.
Related work
-
Related To:
charmcraft#668
(confidence 95%)
The earlier request for status without login was closed as expected behavior because Charmhub operations required authentication; this issue revisits that limitation with a proposed public-data path.
-
Related To:
charmcraft#1124
(confidence 88%)
Analogous public-access work enabled anonymous charm-library fetching in PR #1037 (commit 7476765b), but did not resolve status access.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #668 `charmcraft status` should work without needing to log in | charmcraft | closed | Closed by facundobatista (2022-02-16) as out of Charmcraft's hands: `status` is backed by Charmhub APIs, which require authentication. No code change made; login remains mandatory. | |
| #185 Implement `charmcraft status <charmname>` | charmcraft | closed | Left unimplemented by Store design: the API prevented the requested status lookup, so discussion moved to snapstore-server#1933250 and the request was closed. |