Allow `charmcraft status anycharm` for everyone

Metadata

Project: charmcraft
Number: #1652
Type: issue
State: open
Author: taurus-forever
Labels: —
Created: 2024-04-15 04:19 PM UTC
Updated: 2025-08-15 03:18 PM UTC
Closed: —

Current evaluation

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.

Suggested action: needs triage

Reason: The issue has no labels, no assignee, and no resolution. A maintainer (lengau) engaged in April 2024 with a substantive question about whether the consumer API would suffice, and the reporter responded with detailed usability arguments, but the conversation stalled with no decision. The code still calls the publisher-scoped `/v1/charm/{name}/releases` endpoint (store.py list_releases), confirming the feature has not been implemented. This requires a product/architectural decision about which data to expose anonymously, so it needs triage rather than closure.

Impact: 40 Quick Win: 16.0 Staleness: 75 Complexity: 60 Confidence: 70 Support Request: 20

Issue body

### What needs to get done Hi, At the moment `charmcraft status anycharm` can be executed by the charm maintainer/publisher/collaborator only. All the rest are rejected: ``` > charmcraft status grafana-agent Store operation failed: - permission-required: No publisher or collaborator permission for the grafana-agent charm package ``` ### Why it needs to get done Allowing read status access will avoid bugreports like [this](https://github.com/canonical/grafana-agent-operator/issues/89) (wrong revision chosen as [invisible on charmhub](https://github.com/canonical/charmhub.io/issues/1793)). Can anonymous read access be allowed for `charmcraft status`? Thank you!

Evaluation history

Date	Model	Scores	Action	Summary
2026-09-01 12:29 AM UTC	qwen/qwen3.8-27b	Impact: 40 Quick Win: 16.0 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.
2026-07-22 11:47 AM UTC	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.
2026-07-07 10:39 PM UTC	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.
2026-07-05 04:25 AM UTC	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.
2026-06-16 12:55 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 85 Complexity: 40 Confidence: 75 Support Request: 15	close stale	Requests unauthenticated access to charmcraft status for any charm. Currently restricted to maintainers. Under discussion after a maintainer questioned its value versus juju info. Internal ticket created, but issue remains open with no decision.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.