Every Chrome extension, CLI plugin, VS Code extension, and managed package in your Salesforce workflow runs with the same access you have. If your team does not vet open source tools before they reach production, one compromised update can expose your data without an attacker ever touching your password or MFA. Nicolas Vuillamy compares it to handing the keys to your home to a stranger on the street.
In this session of Salesforce Security Office Hours, Nicolas Vuillamy, CTO France at Cloudity and creator of the open source projects sfdx-hardis and MegaLinter, joins host Matt Meyers, Salesforce CTA and CoFounder and CEO of EzProtect. Together they show Salesforce admins, developers, and architects what to check before installing anything.
Public source code is the first test when you vet open source tools
At 30:34, Nicolas tells the story of a LinkedIn post promoting a new Chrome extension for production orgs, with no link to its source code. His verdict was simple: “Someone claiming to do open source but not showing the source? No way.” He then lays out the rest of his checklist, including repository activity, adoption, and whether the maintainer has a reputation to protect. Free tools like OpenSSF Scorecard automate many of these signals for any public repository.
A stolen token is worth more to attackers than your password
Attackers go after the authentication tokens stored on your laptop because a token skips the password and MFA prompt entirely. The default Salesforce CLI connected app issues refresh tokens that never expire, and Salesforce recommends setting them to expire after 90 days or fewer. At 28:22, Nicolas explains why he sets a much shorter window and calls it a five second change. He also shares the questions he asks every AppExchange vendor, from IP ranges to the exact permissions their integration user needs.
Even trusted tools need a delay before production
Nicolas explains how popular packages, and even security scanners like Trivy, have been compromised, so a trusted name is not enough. He recommends delaying non-security upgrades so the community can catch a bad release, while Matt argues at 48:33 for blocking auto updates until your team has tested them. Matt also shows how a tampered JavaScript library uploaded as a static resource can load on every page of an Experience Cloud site.
Open source remains the smarter choice for Salesforce teams that vet every tool before it reaches production. Watch the full replay for Nicolas’s six-question checklist, the live debate on auto updates, and his answer on whether AI can do the vetting for you.
Your Salesforce data is invaluable—is it truly secure? If you are allowing users to upload files into your Salesforce orgs, you are risk of also uploaded viruses and consequential data breaches. Get in contact with us today.