aws/amazon-q-developer-cli
✨ Agentic chat experience in your terminal. Build applications using natural language.
2k stars · 442 forks · Rust
Healthy
Healthy: no known risks in the checks that ran.
Why
No rule fired.
What would change this
- A dormant maintenance status, a deprecated or archived package, a successor link, or a critical advisory would change this.
Maintenance
CompleteSlowing
- Human commits, 30 days
- 0
- Human commits, 90 days
- 0
- Human commits, 365 days
- 58
- Bot share of commits, 365 days
- 0%
- Last commit
- Apr 23, 2026 (5 months ago)
- Last human commit
- Apr 23, 2026 (5 months ago)
- Authors, 90 days
- 0
- Last release
- Nov 17, 2025 (11 months ago)
- Median PR merge time
- under an hour
Responsiveness: of 30 recent issues, 0% got a maintainer reply. Median first response: n/a.
Sources: Commits, Releases, Merged pull requests, Issues
People
Complete- Owner
- Organization
- Commits sampled
- 58 since Oct 15, 2025
- Authors for half of commits
- 3
- Authors for 80% of commits
- 11
- Contributors
- 79
Top committers
- dingfeli: 22% of commits
- brandonskiser: 21% of commits
- evanliu048: 7% of commits
- kkashilk: 7% of commits
- zixlin7: 5% of commits
Sources: Commits, Contributors
Stars
CompleteOrganic, confidence high
Bursts
- Jul 16, 2025 to Jul 17, 2025: about 130 more stars than usual, peak 124 in one day, a spike that tapers off. Outside explanation: a jump in forks.
Anyone can buy stars for any repo; bursts alone don't prove the owner did.
- The star history looks organic.
Sources: How star history is analyzed
Risk
CompleteFlags
No risk flags.
License
- Now
- Apache-2.0 (OSI-approved)
- A year ago
- Not known
Packages
No published packages found.
Sources: GitHub: aws/amazon-q-developer-cli
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/aws/amazon-q-developer-cli)Earlier verdicts
- Oct 15, 2026: Healthy
- Oct 14, 2026: Healthy
Computed 2 hours ago · method 2026.10.2