repomix-explorer@0.1.0
CAUTION· static onlyPublisher claims: "Use this skill when the user wants to analyze or explore a codebase (remote repository or local repository) using Repomix. Triggers on: 'analyze this repo',..." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-21 and scored it 67/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
npx repomix@latest --remote <repo> --output /tmp/<repo-name>-analysis.xmlFix: Pin versions and sources; vendor anything fetched at install time.- Local directory: `npx repomix@latest [directory]`Fix: Pin versions and sources; vendor anything fetched at install time.- Remote repository: `npx repomix@latest --remote <repo>`Fix: Pin versions and sources; vendor anything fetched at install time.npx repomix@latest --remote yamadashy/repomix --output /tmp/repomix-analysis.xmlFix: Pin versions and sources; vendor anything fetched at install time.npx repomix@latest [directory] [options]Fix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim kongyo2: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.