Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CLI manual presents unimplemented bindings as generators

Closed
  • Is something wrong?
#2,722 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
cli, documentation

Research direction

Start at the stellar contract bindings CLI entry point and inspect the generated descriptions for Python, Java, Flutter, Swift, and PHP. Reproduce the commands against the v28.0.0 release to confirm their not-implemented output. Done means the shipped help no longer presents these bindings as available generators and points users to the external alternative, or removes the placeholder commands.

Written by the indexing model from the issue text.

Description

[!NOTE]
Automated notice: Stellar Raven filed this issue from its automated evaluation pipeline. The issue includes evidence and a public source record. Please verify the live surface before you act.

Finding

The generated CLI manual lists five placeholder languages as binding generators.
Each command exits before generating bindings in Stellar CLI 28.0.0.

The page therefore advertises unavailable built-in capability.
This caused a candidate answer to claim support for Python and Java.

Evidence

On 2026-09-08, the manual listed Python, Java, Flutter, Swift, and PHP under stellar contract bindings.
The current v28.0.0 CLI reported that each generator is not implemented in stellar-cli.
Each error directed users to the external Lightsail Network tool.

On 2026-09-04, Rust and TypeScript accepted their documented input forms in v27.1.0.
The defect affects only the placeholder-language descriptions.

Additional recorded evidence:

  • 2026-09-08 fresh execution used the current v28.0.0 release binary, SHA-256 10c5abc3796505626c098583b4bdc6d4bf52dd50157aa710c62e3d9cb348326b. python, java, flutter, swift, and php each exited 1 with the same not-implemented error. The current generated manual still labels them as generators; rendered SHA-256 96d0a29ea5598340d1289165354f48ce94be8c063a054b9ff022429f73ca1170.
  • 2026-09-04 live read of https://developers.stellar.org/docs/tools/cli/stellar-cli lists Python, Java, Flutter, Swift, and PHP under Generate bindings
  • 2026-09-04 local read-only run of stellar 27.1.0 showed each listed placeholder command exits with a not implemented error and links to https://github.com/lightsail-network/stellar-contract-bindings
  • eval/qa/results/2026-09-04T05-40-51-variantA.json row q-soroban-cli-bindings presented placeholder languages as built-in generators and received a wrong verdict
  • .agents/rounds/2026-09-03-truth-maintenance/upstream-docs-findings-terra.md records the dated recheck

Recommendation

Mark each placeholder language as not implemented in the generated command description.
Link the external tool as an alternative.
Or remove the placeholder commands from the shipped CLI help until implementation exists.

Source Record

Raven recorded this finding as sd-052 (stellar-docs, discovered 2026-09-04).

Public source record: improvements/stellar-docs/sd-052-cli-bindings-placeholder-languages.md

Immutable source snapshot: 8af90c173d8f

Resolution Handoff

When you deploy a fix, link the resolving issue or pull request to the source record.
Then notify Raven through:

https://github.com/stellar-experimental/stellar-raven/issues/new?template=upstream-improvement-ready.yml&title=%5Bupstream-ready%5D%20sd-052%3A%20

Include the finding ID and the resolving issue or pull request.
Include the deployed version or timestamp. Include the smallest live recheck.
Raven verifies the live surface before it sets the finding to fixed-upstream.
An issue closure or merged pull request does not prove the fix.
A separate reviewer repeats the live check before Raven retires the active finding.
Raven keeps a commit-pinned snapshot when one is available.

Dominant language
Rust
Stars
123
Forks
147
Avg merge
3d 11h
Merged PRs (30d)
39

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stellar/stellar-cli

All issues in stellar/stellar-cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.