Nostrweet
C 65 completed
Other
monorepo / rust · small
66
Files
13,247
LOC
0
Frameworks
6
Languages
Pipeline State
completedRun ID
#1545537Phase
doneProgress
0%Started
2026-04-16 23:25:51Finished
2026-04-16 23:25:51LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
39.40Framework unique
—Isolation
—Last stage change
2026-05-10 03:34:40Deduplication group #47293
Member of a group with 813 similar repo(s) — canonical #1436510 view group →
Generated by Repobility's multi-pass static-analysis pipeline (https://repobility.com)
🧪 Code Distillation
Browse all specs →AI Prompt
Create a Rust CLI tool called Nostrweet. This tool needs to download tweets, including all associated media, from Twitter using a Bearer Token. It should also be able to fetch multiple tweets from user timelines with smart pagination and download user profiles. Crucially, it must then convert these tweets into Nostr events and publish them to multiple Nostr relays using a provided mnemonic. The tool should manage local caching efficiently, handle retweets and replies with full context, and support specifying a custom data directory.
rust cli twitter nostr command-line automation social-media api
Generated by gemma4:latest
Catalog Information
Create a Rust CLI tool called Nostrweet. This tool needs to download tweets, including all associated media, from Twitter using a Bearer Token. It should also be able to fetch multiple tweets from user timelines with smart pagination and download user profiles. Crucially, it must then convert these tweets into Nostr events and publish them to multiple Nostr relays using a provided mnemonic. The tool should manage local caching efficiently, handle retweets and replies with full context, and suppo
Tags
rust cli twitter nostr command-line automation social-media api
Quality Score
C
64.7/100
Structure
68
Code Quality
60
Documentation
39
Testing
85
Practices
70
Security
70
Dependencies
80
Strengths
- CI/CD pipeline configured (github_actions)
- Good test coverage (75% test-to-source ratio)
- Consistent naming conventions (snake_case)
- Properly licensed project
Weaknesses
- Potential hardcoded secrets in 3 files
- 768 duplicate lines detected — consider DRY refactoring
- 4 'god files' with >500 LOC need decomposition
Recommendations
- Add a linter configuration to enforce code style consistency
- Move hardcoded secrets to environment variables or a secrets manager
Languages
Frameworks
None detected
Symbols
function368
struct95
extension76
type_alias13
trait8
constant7
enum6
Embed Badge
Add to your README:
