scribetoany@1.0.0
CAUTIONPublisher claims: "Transcribe local audio or video files (MP3, M4A, WAV, MP4, MOV, WEBM…) or public X, Twitch, Loom, Google Drive and Dropbox links into text, SRT or VTT subtitles with the ScribeToAny CLI, with timestamps and optional speaker labels. Use when the user asks to transcribe a recording, meeting, interview, podcast, lecture or video on their computer, turn speech into text, or make subtitles or captions for a media file; also for "转写", "转文字", "做字幕", "语音转文字". Not for editing existing subtitle files." Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-06 and scored it 69/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
No other findings across 162 lines in 2 files.
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
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim hypercube67-formal: 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.