HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
huseyinbabal
taws
Rust2026–2026
huseyinbabal / taws

taws

Terminal UI for AWS (taws) - A terminal-based AWS resource viewer and manager

3Distinct people
6Mentions
0Explicit recommenders
2.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Terminal UI for AWS (taws) - A terminal-based AWS resource viewer and manager

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval6 dated mentions

Observed mentions: 2026-01-04 20:17:22 UTC to 2026-01-07 11:59:39 UTC.

0122026-01-04 18:00:00 UTC to 2026-01-04 21:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 4, 18:002026-01-04 21:00:00 UTC to 2026-01-05 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-01-05 00:00:00 UTC to 2026-01-05 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-05 03:00:00 UTC to 2026-01-05 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-05 06:00:00 UTC to 2026-01-05 09:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-05 09:00:00 UTC to 2026-01-05 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-05 12:00:00 UTC to 2026-01-05 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-05 15:00:00 UTC to 2026-01-05 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-05 18:00:00 UTC to 2026-01-05 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-05 21:00:00 UTC to 2026-01-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 00:00:00 UTC to 2026-01-06 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 6, 00:002026-01-06 03:00:00 UTC to 2026-01-06 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 06:00:00 UTC to 2026-01-06 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 09:00:00 UTC to 2026-01-06 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 12:00:00 UTC to 2026-01-06 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 15:00:00 UTC to 2026-01-06 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 18:00:00 UTC to 2026-01-06 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 21:00:00 UTC to 2026-01-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-07 00:00:00 UTC to 2026-01-07 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-07 03:00:00 UTC to 2026-01-07 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-07 06:00:00 UTC to 2026-01-07 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-07 09:00:00 UTC to 2026-01-07 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 7, 09:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 4, 18:002026-01-04 18:00:00 UTC2026-01-04 21:00:00 UTC110
Jan 4, 21:002026-01-04 21:00:00 UTC2026-01-05 00:00:00 UTC202
Jan 5, 00:002026-01-05 00:00:00 UTC2026-01-05 03:00:00 UTC000
Jan 5, 03:002026-01-05 03:00:00 UTC2026-01-05 06:00:00 UTC000
Jan 5, 06:002026-01-05 06:00:00 UTC2026-01-05 09:00:00 UTC101
Jan 5, 09:002026-01-05 09:00:00 UTC2026-01-05 12:00:00 UTC101
Jan 5, 12:002026-01-05 12:00:00 UTC2026-01-05 15:00:00 UTC000
Jan 5, 15:002026-01-05 15:00:00 UTC2026-01-05 18:00:00 UTC000
Jan 5, 18:002026-01-05 18:00:00 UTC2026-01-05 21:00:00 UTC000
Jan 5, 21:002026-01-05 21:00:00 UTC2026-01-06 00:00:00 UTC000
Jan 6, 00:002026-01-06 00:00:00 UTC2026-01-06 03:00:00 UTC000
Jan 6, 03:002026-01-06 03:00:00 UTC2026-01-06 06:00:00 UTC000
Jan 6, 06:002026-01-06 06:00:00 UTC2026-01-06 09:00:00 UTC000
Jan 6, 09:002026-01-06 09:00:00 UTC2026-01-06 12:00:00 UTC000
Jan 6, 12:002026-01-06 12:00:00 UTC2026-01-06 15:00:00 UTC000
Jan 6, 15:002026-01-06 15:00:00 UTC2026-01-06 18:00:00 UTC000
Jan 6, 18:002026-01-06 18:00:00 UTC2026-01-06 21:00:00 UTC000
Jan 6, 21:002026-01-06 21:00:00 UTC2026-01-07 00:00:00 UTC000
Jan 7, 00:002026-01-07 00:00:00 UTC2026-01-07 03:00:00 UTC000
Jan 7, 03:002026-01-07 03:00:00 UTC2026-01-07 06:00:00 UTC000
Jan 7, 06:002026-01-07 06:00:00 UTC2026-01-07 09:00:00 UTC000
Jan 7, 09:002026-01-07 09:00:00 UTC2026-01-07 12:00:00 UTC101

What Hacker News says

6 sources
The more you see and review LLM-generated code, the more you can detect its fingerprints. Obviously you're not going to prove this is LLM-generated. I wouldn't bet $1M that it is. This could be 100% human made. But read the same link from above: https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52.... LLMs leave temporal comments like "// Now do X", or "// Do X using the new Y", as responses to prompts like "Can you do X with Y instead?". or below: "// Auto-refresh every 5 seconds (only in Normal mode)". I would guess this comment was during a response to a prompt like: "can you only auto-refresh in Normal mode?" Sometimes there are tautological comments and sometimes not: https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52... ``` // Get log file path let log_path = get_log_path(); ``` This is another signal to me that th
Read the rest
ere is less human influence over the project. No, none of these are a smoking gun. Also none of this means it was completely vibe coded. To me personally, the worrying part is that these patterns signal that perhaps human eyes were never on that section of the code, or at least the code was not considered carefully. For a toy app, who cares? For something that ingests your AWS creds, it's more of a red flag. Edit: changed the language a bit to sound less sardonic. My comment is more about LLM signals than a judgment on LLM usage.
In Show HN: Terminal UI for AWS
Easiest one is ridiculous comments, always a dead ringer for an LLM. ESPECIALLY when its from a plan and comments '// STEP 2: ...' Like here in this posts repo https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52... This a dead ringer for LLM slop that someone didnt even care enough to go through and clean up. Edit: Just to keep it going, you ever seen a human write dependencies like this for a small toy tui? https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52... Edit2: Sure why not, lets reimplement randomly a custom jsonpath when serde_json_path exists https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52...
In Show HN: Terminal UI for AWS

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.