recme@1.0.2
CAUTION· startup onlyPublisher claims: "Enables Claude to drive a Windows screen recorder: start and stop captures of the desktop, a display, region, saved area or window, review screenshots and frames, trim and reorder clips, extract audio, compress to a size limit, and send files to nearby devices over Wi-Fi. Includes token-protected localhost access with optional confirmation for sensitive actions like sending and deleting." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
- Needs
- RECME_TOKEN — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
RECME_TOKENConfiguration, not credentials: FFMPEG_PATH, FFPROBE_PATH, RECME_CONFIG_DIR, RECME_MAC_ARCH, RECME_URL- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard. It asks for RECME_TOKEN and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-12 and scored it 68/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: README tells the reader to click past SmartScreen; Access to sensitive file paths; README directs the reader to a committed installer. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 45 s · 2 scenarios · 0 deviationsStatic findings
Open the newest release at the top (it is a **beta**), download **`Recme-Setup-<version>.exe`** from *Assets*, run it, done (ffmpeg is included; no other install needed). Windows 10/11, 64-bit. The inFix: Pin versions and sources; vendor anything fetched at install time.console.log('send (no device) :', await t('send_recording', { name, device: 'nonexistent-device' }));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.const run = (args, env = {}) => spawnSync(process.execPath, [path.join(__dirname, '..', 'src', 'cli.js'), ...args], { encoding: 'utf8', env: { ...process.env, ...env } });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.mcpServer = await startMcpHttp({Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.Open the newest release at the top (it is a **beta**), download **`Recme-Setup-<version>.exe`** from *Assets*, run it, done (ffmpeg is included; no other install needed). Windows 10/11, 64-bit. The inFix: Pin versions and sources; vendor anything fetched at install time.…a separate program (it does not link to it). If you redistribute the installer, you must follow the GPL for the bundled FFmpeg (keep the license text, and make the correspondi…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Open the newest release at the top (it is a **beta**), download **`Recme-Setup-<version>.exe`** from *Assets*, run it, done (ffmpeg is included; no other install needed). Windows 10/11, 64-bit. The inFix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
12 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- README tells the reader to click past SmartScreen≈ +9 on the totalPin versions and sources; vendor anything fetched at install time.
- README directs the reader to a committed installer≈ +9 on the totalPin versions and sources; vendor anything fetched at install time.
- README tells the reader to bypass SmartScreen≈ +9 on the totalPin versions and sources; vendor anything fetched at install time.
- Unclaimed publisher≈ +8 on the totalClaim bizcuit47: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.