simple-git
4.1.0 · 16 Nov 2026MIT15.5M / weekRepositorynpmAtom feed
Where each line stands
Plan an upgradeLatest releases
All 278 releases- 4.x · latest line
4.1.0
16 Nov 2026Summary· from the note as AI read it
Upgrade: this release fixes a security issue.
Minor Changes
Add the
allowConfigandstrictoptions. Configuration keys outside the built-in list of known-safe keys
(SAFE_CONFIG_KEYS) and the keys named inallowConfignow emit a one-offSIMPLE_GIT_UNLISTED_CONFIGwarning,
or are rejected whenstrict: trueis set. Known-unsafe keys can now be permitted individually throughallowConfig, and environment variables throughallowEnvironment, deprecating theunsafe.allowUnsafe*options
that only covered configuration keys or environment variables (they continue to work as before).The custom binary (the first string of the
binaryoption orgit.customBinary()) may now contain spaces
when it looks like a path to a file, for exampleC:\Program Files\Git\bin\git.exe. The value must include
a path separator and no part of the path may start or end with a space. The prefix (the optional second string)
remains limited to the existing restricted character set, as it is passed to the binary as its first argument.When the recommended checks are enabled (with
unsafe.recommended: trueorstrict: true),HOMEandXDG_CONFIG_HOME
supplied through.env()with a value other than the one inprocess.envrequireallowUnsafeConfigPaths
(or naming them inallowEnvironment), asgitreads the global configuration from$HOME/.gitconfigand$XDG_CONFIG_HOME/git/configin the same way asGIT_CONFIG_GLOBAL. Passing the inherited value through is unaffected,
and neither is removed from the inherited environment.parseEnvaccepts the inherited environment as an optional second argument, used to compareHOMEandXDG_CONFIG_HOMEagainst.isGuardedEnvKeyis now exported from@simple-git/argv-parser, identifying the environment variables
(GIT_*and the othersgitreads, such asEDITORandPAGER) thatsimple-gitremoves from an inherited
environment.Settle on the use of
strictto refer to thesimpleGitconfiguration setting to enable strict controls,
applying to both Git impacting environment variables and writing to the Git config.Use of the
strictmode also implies the use ofunsafe.recommendedVulnerability reports:
With thanks to @manus-pi, @manus-use, @ba-am, @mspiq, @hoseinenddev, @freyesperales, @dalberrt,
@zer0d4y5, @gamster01, @humaneBicycle, @Hama1cco, @eliteaja11-dev, @Cone-Tester, @Figo5, @MalwareEZ,
@zachariah-mithani, @shaswata56, @Akokonunes for submitting CVE proposals that contributed to these changes.closing the loop on any configuration setting ending with
.cmdorcommandunder the catch-allallowUnsafeCommandBinariessetting (only enforced with the newunsafe.recommendedoption, orstrict), and blockinggpg.ssh.defaultKeyCommandunderallowUnsafeGpgProgram.allowUnsafePagerwill now catch setting a custom binary ingit grep --open-files-in-pager.allowUnsafePagernow also coversinteractive.diffFilter, the shell command thatgit add -pand the other--patchcommands pipe their diff through.new (deprecated on arrival, prefer
allowConfig)allowUnsafeSendEmailConfigoption covering thesendemail.*keys thatgit send-emailruns as commands, reads as files or uses to turn off certificate verification (sendmailCmd,toCmd,ccCmd,headerCmd,smtpServer,smtpServerOption,smtpSSLCertPath,smtpSSLClientCert,smtpSSLClientKey,aliasesFileandmailmap.file, including their per-identitysendemail.<identity>.*variants), and theimap.tunnel,imap.hostandimap.sslVerifykeys used bygit imap-send.new (deprecated on arrival, prefer
allowConfig)allowUnsafeWebServerConfigoption covering theinstaweb.httpd,instaweb.modulePathandinstaweb.gitwebDirkeys used bygit instaweb.new (deprecated on arrival, prefer
allowConfig)allowUnsafeBrowseroption covering thebrowser.<tool>.path,browser.<tool>.cmd,man.<tool>.pathandman.<tool>.cmdkeys used bygit helpandgit instawebto open a browser or man page viewer.browser.<tool>.cmdandman.<tool>.cmdwere previously covered byallowUnsafeCommandBinaries.new (deprecated on arrival, prefer
allowConfig)allowUnsafeSignatureTrustoption coveringgpg.ssh.allowedSignersFile,gpg.ssh.revocationFileandgpg.minTrustLevel, which decide which signatures pass verification.allowUnsafePacknow blocks--execfor every command other thanrebase, as it names the remote program forpush,send-pack,fetch-pack,archive --remoteandls-remote(previously onlypush).new
allowUnsafeConfigRenameoption blockinggit config --rename-section/git config rename-section, which could move keys written under a harmless section name (eg:foo.fsmonitor) into one that runs commands (core.fsmonitor).allowUnsafeExecnow also covers thegit filter-branchoptions that run a shell command:--setup,--env-filter,--tree-filter,--index-filter,--parent-filter,--msg-filter,--commit-filterand--tag-name-filter.allowUnsafeDiffExternalnow also coversdifftool.<tool>.path, matchingmergetool.<tool>.pathunderallowUnsafeMergeDriver.
Patch Changes
Add a security policy describing which inputs are safe for untrusted data.
4.0.2
26 Sep 2026Add
VISUALenvironment variable to set ofallowUnsafeEditorenvironment variables.
Patch Changes
Add
VISUALenvironment variable to set ofallowUnsafeEditorenvironment variables.
4.0.1
25 Sep 2026Prepare package.json before publishing.
Dependency tracking
Know when your own dependencies move
simple-git had 6 security advisories in the last 12 months. inlinr emails you the day one touches a project of yours, with the version that fixes it.
Advisories reach you
An email when a critical or high advisory affects a project, before the next install.
Upgrades checked first
Peer ranges, Node, ESM-only and types changes read before you bump.
Only what matters
Majors and breaking notes stay; patches and sibling bumps fold into one line.
Reading releases, release notes and advisories…
Registry facts last checked 20 Nov 2026. Releases and advisories last read 20 Nov 2026.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.