LF-Engineering/sync-data-sources: sources/cmd/syncdatasources/syncdatasources.go; 4 LoC

Found a possible issue in [LF-Engineering/sync-data-sources](https://www.github.com/LF-Engineering/sync-data-sources) at [sources/cmd/syncdatasources/syncdatasources.go](https://github.com/LF-Engineering/sync-data-sources/blob/84b6756e50203a3c0af3aa75e900031fb9fefab8/sources/cmd/syncdatasources/syncdatasources.go#L323-L326)

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.

>

[Click here to see the code in its original context.](https://github.com/LF-Engineering/sync-data-sources/blob/84b6756e50203a3c0af3aa75e900031fb9fefab8/sources/cmd/syncdatasources/syncdatasources.go#L323-L326)

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

```go
for index, dataSource := range fixture.DataSources {
validateDataSource(ctx, fixture, index, &dataSource)
nEndpoints += len(dataSource.Endpoints)
}

```

Click here to show extra information the analyzer produced.

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {validateDataSource 4} was not found in the callgraph; reference was passed directly to third-party code
```

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: 84b6756e50203a3c0af3aa75e900031fb9fefab8

Start with sources/cmd/syncdatasources/syncdatasources.go at lines 323-326, then inspect validateDataSource and how the dataSource pointer is used. Determine whether the range variable's address can escape or reach third-party code, and classify the finding as a bug, mitigated, or desirable behavior.

Written by the indexing model from the issue text.