soma@1.1.0
CAUTION· static onlyPublisher claims: "Expert guide for participating in the SOMA network — a decentralized system that trains a foundation model through competition. Provides data submission work..." 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.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-20 and scored it 57/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; Pipe-to-shell pattern; Access to sensitive file paths. 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
1. Install soma CLI (`curl -fsSL https://sup.soma.org | bash && sup install soma`)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.curl -fsSL https://sup.soma.org | bash && sup install somaFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.…gning, dataset access, and artifact storage. Credentials are stored in a local `.env` file (gitignored) and pushed to Modal's encrypted secret store — never committ…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.1. Install soma CLI (`curl -fsSL https://sup.soma.org | bash && sup install soma`)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.cp .env.example .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Fill in `.env`. Each credential is required — here's what it does and where to get it:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…CESS_KEY (sensitive), S3_ENDPOINT_URL, S3_PUBLIC_URL. All credentials stored in .env (gitignored) and pushed to Modal encrypted secret store. Use testnet keys only.…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.curl -fsSL https://sup.soma.org | bash && sup install somaFix: 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
23 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim cfuaqz: 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.
- 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.
- Remote installer piped to shell≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.