incorrect gem version

[pombredanne]

We get pkg:gem/elasticsearch-api@Elasticsearch::API::VERSION and
pkg:gem/elasticsearch-api@Elasticsearch::API::VERSION?uuid=5e6ab586-9674-4f11-b9cb-75f384d8594b when parsing a gemspec. See https://github.com/elastic/elasticsearch-ruby/blob/f745eddd3b4332cf365c5df53f482a86a05ae96b/elasticsearch-api/elasticsearch-api.gemspec#L25
We may be able to recover from this.

[pombredanne]

See also:

• excon https://github.com/excon/excon/blob/17ed91945ea07d781a984a31411d6adf814bf53e/excon.gemspec#L2
• faraday https://github.com/lostisland/faraday/blob/36916f07596f6e1ab71b688be56e5e087a1372df/faraday.gemspec

[kumarasantosh]

Hi @pombredanne, I'd like to work on this issue.

I've been actively contributing to scancode-toolkit recently with
PRs for NuGet deps.json (#4803), Conda environment.yml (#4804),
Cargo deny.toml (#4805), Bazel MODULE.bazel (#4806) and Gradle
.module files (#4807).

I've confirmed the bug still exists — gemspecs using Ruby constants
like Elasticsearch::API::VERSION are stored as-is instead of being
handled gracefully. I will raise a pr soon.