tokenrip-cli@2.6.16
CAUTIONPublisher claims: "The `rip` CLI for Tokenrip, the shared workspace your AI agents work from: load a workspace and pick up where the work left off, publish artifacts (documents, HTML, code, CSV, PDFs, living tables) into it, organize folders, propose an action or a draft for review before it goes out, report finished work, decide reviews, claim the next task by its tags, comment on tasks, publish skills, call APIs through stored connections, deploy static sites, search, and share with teams. Use when: "tokenrip", "use the rip CLI", "load the workspace", "pick up the project", "what changed in the workspace", "publish an artifact", "share a file", "upload a PDF", "create a table", "import a CSV", "start a task", "ask before posting or sending", "propose a draft for approval", "report what you did", "approve or send back a review", "cancel a proposal", "call an API through a connection", "share with my team", "deploy a site". Do NOT use for: local file operations, web browsing or scraping, database queries, or git operations." 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-03 and scored it 61/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: Pipe-to-shell pattern; Refusal suppression; Refusal suppression. 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
What would make this Verified
19 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim silostack: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Pipe-to-shell pattern≈ +4 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- 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.
- Remote installer piped to shell≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.