vscode-opentofu This Week: Security Dependency Bumps and a Workspace Indexing Setting
The vscode-opentofu extension, the VS Code language support for OpenTofu, had a quiet but useful week. All three commits landed on November 10 and they cover two things users care about: patched dependencies and better control over which directories the indexer scans. The headline change is a dependency update that fixes multiple security issues.
Security focused dependency bump
The largest change of the week is the commit behind the security dependency update (#149), which touched package.json and package-lock.json only. The diff shows 425 insertions and 342 deletions across the lockfile, which is the usual shape of a transitive dependency refresh.
Notable moves visible in the diff:
@azure/identitygoes from 4.13.2 to 4.14.1, which pulls in@azure/msal-node7.2.1 and@azure/msal-common16.16.1openis bumped from 10.x to 11.x as a transitive requirement- Several copies of
brace-expansionmove to newer patched versions @nodable/entitiesis dropped from the tree entirely
None of this changes extension behavior directly. It matters because the extension ships these packages to every user who installs it from the marketplace. Running stale copies of auth and URI parsing libraries inside an editor extension is the kind of exposure nobody wants. If you auto update extensions, you get this without action; otherwise, update manually.
Workspace level ignoreDirectoryNames
Indexing got a small but practical improvement. The commit behind the workspace settings change (#147) allows indexing.ignoreDirectoryNames to be set at the workspace level, not only at user level.
{
"opentofu.indexing.ignoreDirectoryNames": [".terraform", "modules/vendor"]
}
Until now, teams sharing a repo could not agree on which directories to skip without everyone changing their personal settings. Workspace scoped configuration fixes that: commit the setting in .vscode/settings.json and every contributor gets the same indexing behavior. This is the kind of footgun fix that saves a support thread or two.
CI portability: Playwright on Ubuntu 26.04
The third change is small and it is for contributors rather than users. The Playwright bump (#148) updates the test runner to a version that supports Ubuntu 26.04, so the extension’s e2e tests keep running on newer CI images. No user facing impact, but it keeps the project’s test pipeline from aging out of its CI base image.
What to watch
- If you pin extensions with a policy tool, look for a new release of vscode-opentofu containing these November 10 commits so the security bumps reach your fleet.
indexing.ignoreDirectoryNamesat workspace scope is worth committing to shared repos with vendored modules; large ignored trees can cut indexing time noticeably.- Expect further transitive dependency refreshes. The lockfile churn this week shows the maintainers are treating npm audit output as a trigger, not an annual chore.
You can read the full commit history on the GitHub repository.