cloudrkt/statuspage-cli: cmd/component.go; 3 LoC

Found a possible issue in [cloudrkt/statuspage-cli](https://www.github.com/cloudrkt/statuspage-cli) at [cmd/component.go](https://github.com/cloudrkt/statuspage-cli/blob/7c5f87bd66a4f395eb2423e369d61160e5a43814/cmd/component.go#L27-L29)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> reference to component was used in a composite literal at line 28

[Click here to see the code in its original context.](https://github.com/cloudrkt/statuspage-cli/blob/7c5f87bd66a4f395eb2423e369d61160e5a43814/cmd/component.go#L27-L29)

Click here to show the 3 line(s) of Go which triggered the analyzer.

```go
for _, component := range components {
fmt.Println(&component)
}

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: 7c5f87bd66a4f395eb2423e369d61160e5a43814

Start with cmd/component.go lines 27-29 and the linked code context in the cloudrkt/statuspage-cli repository. Check whether the reported reference to the range variable represents a bug, is mitigated, or is desirable behavior, then classify the finding with the corresponding issue reaction.

Written by the indexing model from the issue text.