salesforce-easy@1.0.17
CAUTION· static onlyPublisher claims: "Complete Salesforce CRM integration for real-time data access, lead management, opportunity tracking, duplicate detection, and bulk operations. One-click OAu..." 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-22 and scored it 58/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: Access to sensitive file paths; Access to sensitive file paths; 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
# .env file (never commit to source control)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.**Option C — Username + security token (.env):**Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# 2. Configure credentials in .env (never export raw secrets in shell)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Never pass secrets as command-line arguments.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.return True, "Token refreshed — update SALESFORCE_ACCESS_TOKEN in your .env", {Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Copy .env.example to .env and fill in your values — see README for details.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<div class="warning-box"> <span class="wi">⚠</span> <div>This method sends your password + security token to Salesforce. Only use it if your org's security poliFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct."SALESFORCE_INSTANCE_URL to your .env file."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Write it to your .env by calling connect.py connect afterward.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.stored in .env, or passed via command line.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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
22 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim sawera557: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- 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.
- Credential pass-through configuration≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.