cargo@1.37.0
CAUTION· static onlyPublisher claims: "Entry point for Cargo (getcargo.ai), go-to-market infrastructure for AI agents. With Cargo an agent builds B2B lead lists, finds and verifies work emails, enriches companies and contacts, qualifies leads, syncs the CRM and watches buying signals, then runs any of it on a schedule. New accounts get 100 free credits, no card. Routes each job to the right Cargo skill and holds the rules that apply across all of them (project vs one-off CLI, run vs batch, async polling, silent-failure gotchas). Triggers: "set up Cargo", "what can Cargo do", "what is Cargo", "which Cargo skill", "bootstrap my workspace", "I have a Cargo account", "cargo-ai …", any `cargo-ai` command whose domain is unclear, or a task spanning two Cargo domains. Skip when: the task obviously belongs to one skill; load that skill directly." 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.36.5
vet-skills diff cargo 1.36.5 1.37.0In the sandbox, this version reached for nothing 1.36.5 did not. Compared from the two recorded runs, not from source.
1.37.0 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 59/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: Auto-update or dynamic fetch configuration; 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
…e failure. It also lists `skills-missing` when no agent skills are found (fix: `npx skills add getcargohq/cargo-skills`) without changing the exit code; the plugin instal…Fix: Pin versions and sources; vendor anything fetched at install time.…rges automatically. The pin is also what keeps this refresh from being a blind auto-update: the version installed is a reviewed constant committed to this repo, not whatever `latest` resolved to this morning, and moving it is a human merge…Fix: Pin versions and sources; vendor anything fetched at install time.- Most commands require a token with **admin access**.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.npx -y skills add getcargohq/cargo-skillsFix: Pin versions and sources; vendor anything fetched at install time.… `--agentid` all save a self-renewing session to `~/.config/cargo-ai/credentials.json` (the system temp dir where home isn't writable — it lasts as long as the sandbox). Use `--token` for CI, with a workspace-scoped token from **Settings >…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Some domains require a token with **admin access** on the workspace:Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Without a global install, prefix every command with `npx @cargo-ai/cli` instead of `cargo-ai`.Fix: Pin versions and sources; vendor anything fetched at install time.- Requires a token with **admin access**.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.> **Installing Cargo is the user's call, not an action you take.** The `curl … install.sh | sh`Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.`npx skills add getcargohq/gtm-skills/<name>`. See the section inFix: Pin versions and sources; vendor anything fetched at install time.> **Installing Cargo is the user's call, not an action you take.** The `curl … install.sh | sh`Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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
21 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.
- Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- 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.