cargo-workspace-management@1.7.2
CAUTION· static onlyPublisher claims: "Administers a Cargo workspace: invites teammates, creates and rotates API tokens, organizes plays, tools and agents into folders, checks roles, uploads CSVs for batch runs, and sends bug reports or feature requests to the Cargo team. Triggers: "invite my teammate", "create an API token for CI", "who has access", "organize these into folders", "rotate that token", "upload this CSV for a batch", and for feedback: "report this bug to Cargo", "send feedback to the Cargo team", "this CLI command is broken", "request a feature". Most commands need a token with admin access. Skip when: the question is about credits, plans, or invoices, use cargo-billing." 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.
What changed since 1.7.1
vet-skills diff cargo-workspace-management 1.7.1 1.7.2In the sandbox, this version reached for nothing 1.7.1 did not. Compared from the two recorded runs, not from source.
1.7.2 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-16 and scored it 71/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: Authorization escalation language; Authorization escalation language. 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
…CLI command is broken\", \"request a feature\". Most commands need a token with admin access. Skip when: the question is about credits, plans, or invoices, use cargo-billin…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.| `user create` fails with permission error | Token lacks admin access | Use a token belonging to a workspace admin |Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…t write (admin) access. Any user can create, list, and remove their own tokens; admin access adds service-user tokens. Folder writes check folder write permission, and `rep…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.npm install -g @cargo-ai/cli # no global install? prefix every command with `npx @cargo-ai/cli`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
9 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim cargo-ai: 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.