Add a "secrets" API
Metadata
Current evaluation
Closed as not planned; build-secrets support was provided through the prototype service instead of the proposed redaction API.
Resolution: closed not a bug
Reason: The issue record says the proposed secrets API was closed as not planned. Build-secrets support was addressed through the prototype service rather than implementing this API.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
This API will let applications define words that are "secrets". When printing, these secrets are replaced with a standard password marker (e.g. `******`).
### Why it needs to get done
This is to support build-secrets in craft applications.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | Closed as not planned; build-secrets support was provided through the prototype service instead of the proposed redaction API. | |
| stealth/space-bunny-alpha | — | closed not a bug | Adding a secrets API was closed as not planned; the planned build-secrets capability was later provided through the prototype service, not the proposed API. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The proposed secrets API for masking sensitive values during printing was closed without implementation or follow-up pull requests. | |
| qwen/qwen3.6-35b-a3b | — | — | Requesting a secrets API to mask sensitive words during printing was closed without implementation or discussion. With zero comments and no resolution details, the feature appears abandoned or rejected. | |
| qwen/qwen3.6-35b-a3b | — | — | The proposed secrets API for masking sensitive output was closed without implementation. With no discussion or linked pull request, the feature request was abandoned. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.