Item detail
github.com

yamadashy/repomix

yamadashy/repomix is an AI project in RepoRadar's Radar section, holding Gold tier and a 'try now' verdict. Its strongest signal is workflow potential, scored 9.9 out of 10.

Score8.8
Popularity23.0
Riskconditional
TierGold
Score breakdown
Usefulness9.0
Novelty7.0
Momentum9.0
Maturity7.3
Open-source/build8.4
Evidence7.2
Workflow potential9.9
Setup ease8.8

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for developers and agent operators who keep losing time on context setup and want a repeatable way to hand a repo to an AI system with fewer missing files, prompt hacks, or copy-paste mistakes.

Who should use it

developers feeding larger repos into coding models agent operators trying to reduce context-prep overhead teams comparing repository-packaging workflows for AI coding power users who want a repeatable prompt-input bundle

Who should skip it

Skip yamadashy/repomix if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.

About this signal

yamadashy/repomix is tracked by RepoRadar as an AI project in the Radar section. First seen 2026-06-20; the source record was last checked on 2026-06-20. The current verdict is 'try now' with a Gold tier and easy setup difficulty. yamadashy/repomix leads on workflow potential (9.9) and practical usefulness (9.0); its lowest signal is novelty (7.0), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The yamadashy/repomix record combines a 8.8/10 composite score with separate popularity (23.0), risk (conditional), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.

Risk explanation

It can package large amounts of proprietary source code for use with third-party AI systems, so review exclusions and sharing boundaries before using it on private repositories.

Evidence links
Closest alternatives / related signals
repo-packaging context-window coding-agent developer-tooling cli
Verification record

What RepoRadar actually verified

Tested in a bounded workflow

Bounded representative workflow retained by RepoRadar verification harness. Last checked 2026-07-13T10:34:19.597411Z.

passed · cohort-20260712-repomix-isolated

Tester
RepoRadar automated local verification harness
Started
2026-07-13T10:34:11.356716Z
Completed
2026-07-13T10:34:19.597411Z
Environment
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
1 minute(s)
Evidence scope
Bounded representative workflow
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
  • Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
  • Created 3 synthetic fixture file(s) inside the disposable work directory; retained hashes prove the exact inputs.
  • Selected only src/** from the disposable repository and requested Repomix's Markdown output format.
  • Validated the packed artifact contained both selected source files and excluded the out-of-scope notes fixture.
  • Executed bounded check: Pack a disposable two-file JavaScript repository into a Markdown context artifact.
  • Captured the complete sanitized stdout, stderr, exit status, artifact checks, and 8.24-second wall time.
Observed results
  • Command exited 0 after 8.24 seconds.
  • Repomix emitted one Markdown context artifact containing both selected JavaScript files while omitting the excluded notes fixture.
  • Validated repomix-output.md: 3 required marker(s) present and 1 excluded marker(s) absent; size and SHA-256 are retained.
Observed strengths
  • The include glob and Markdown formatter produced a deterministic, agent-readable bundle from a disposable repository without needing an account or model provider.
Friction
  • A useful bundle still depends on deliberate include/exclude scope; the workflow explicitly constrained src/** to avoid packing unrelated fixture content.
Limitations
  • This small fixture does not measure large-monorepo performance, compression, remote-repository input, token-budget enforcement, or secret-scanner coverage.
  • This credential-free disposable workflow does not establish production scale, model quality, reliability under sustained use, or team adoption.

Pricing assessment: The tested local CLI workflow used the open-source npm package and no paid Repomix service or model provider.

Privacy assessment: Only synthetic fixture files were read locally; package installation contacted the npm registry, while no repository content was sent to a model or hosted Repomix service.

Open retained test log →

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

45 dated snapshots retained from 2026-06-20 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.8 current · +0.0 net
Repository momentum9.6 current · +0.6 net
GitHub stars (observed)27,820 current · +718 net
GitHub stars27,820 exact observation
Versionv1.18.0
Last release2026-08-08T04:31:26Z
Maintenanceactive
Current riskconditional
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineAnthropic, Claude, Google Gemini, Model Context Protocol, OpenAI

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.89.627,820conditionaltry nowactive
2026-08-128.89.627,796conditionaltry nowactive
2026-08-118.89.627,763conditionaltry nowactive
2026-08-108.89.627,729conditionaltry nowactive
2026-08-098.89.327,711conditionaltry nowactive
2026-08-088.89.627,707conditionaltry nowactive
2026-08-078.89.627,595conditionaltry nowactive
2026-08-068.89.0Not recordedconditionaltry nownot recorded
2026-08-058.89.0Not recordedconditionaltry nownot recorded
2026-08-048.89.627,595conditionaltry nowactive
2026-08-038.89.627,595conditionaltry nowactive
2026-08-028.89.627,575conditionaltry nowactive

Why the record changed

stars changed

Stars changed: 27796 → 27820.

stars changed

Stars changed: 27763 → 27796.

stars changed

Stars changed: 27729 → 27763.

stars changed

Stars changed: 27711 → 27729.

stars changed

Stars changed: 27707 → 27711.

version changed

Version changed: v1.17.0 → v1.18.0.

stars changed

Stars changed: 27595 → 27707.

stars changed

Stars changed: 27575 → 27595.

stars changed

Stars changed: 27555 → 27575.

stars changed

Source-observed stars changed: 27549 → 27555. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Source-observed stars changed: 27548 → 27549. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 27465 → 27481.