SuperCLI Suggest a CLI
中文EN

SuperCLI · Public inclusion standards v1

Choose a useful tool.
Understand the evidence behind it.

Less trial and error between discovery and installation.
We publish original sources, review scope, and missing information so every recommendation can be questioned.

Explore tools with these standards

Two different concepts

Sources identify maintainers. Reviews show what was checked.

Vendor and community tools follow the same inclusion standards. Labels are not quality rankings or vendor endorsements.

Vendor maintained

A CLI maintained directly by the product or platform vendor.

Community project

Maintained by independent authors, open-source organizations, or communities, including original project CLIs.

One standard for all sources

Five things we check

01

Traceable sources

Confirm it is a CLI. Check original authors, maintainers, websites, or repositories. Distinguish upstream projects from mirrors and namesakes.

Public evidence: repositories, documentation, and inclusion pull requests.
02

Evidence for installation

Installation methods must match upstream instructions and use valid links. Source reviews and installation tests are recorded separately; tests require an environment and version.

No installation-test claim without actually running it.
03

Clear purpose and limitations

Describe suitable tasks and check platform, dependency, account, and cost requirements so users know what to prepare.

Be specific about purpose and cite limitations without exaggeration.
04

Visible maintenance status

Check public documentation, licenses, archived status, and updates. Pushes are not releases; identify missing information explicitly.

Stars indicate popularity, not an inclusion quality threshold.
05

Accountable reviews

Record maintainers, dates, scope, and evidence. Recheck changed information; users can report problems through submissions or correction forms.

Reviews describe information at a point in time, not a permanent guarantee.

Reading cards and details

Show only recorded evidence and state exactly what was checked.

Source review
Documentation, original repositories, or installation instructions were reviewed. This does not mean we installed the tool.
Installation tested
Used only when a tool was run and its environment, version, and evidence were recorded.
Review scope pending
Inclusion evidence exists, but detailed reviews are pending. No automatic pass or fail is assigned.

Historical reviews are being added gradually. Existing scope is displayed honestly; no blanket Verified labels are issued.

A directory built on transparency and shared maintenance.

Pull requests receive human review before merging; main is checked and deployed automatically. Scorecard provides repository maturity context, not a replacement for installation tests or security audits.

Suggest a CLIReport incorrect information