Bump typeorm from 0.3.30 to 0.3.31

[dependabot]

Bumps typeorm from 0.3.30 to 0.3.31.

Release notes

Sourced from typeorm's releases.

0.3.31

Bug Fixes

• cache: release query runner on error in storeInCache (#12545) (a84b9b3)
• correct grammar in AlreadyHasActiveConnectionError message (#12554) (304d129)
• entity-manager: default invalidWhereValuesBehavior to throw on the write path (#12690) (44d8052)
• entity-manager: validate where criteria in increment/decrement (#12692) (8a51b75)
• mongodb: use cursor.transform for doc to entity transformation and skip load broadcast in next if toArray (#11926) (0bbefc9)
• move hashing function to PlatformTools (#12648) (c456cbd)
• multiple recursive cte problems (#12490) (7c26654)
• normalization of FindOptionsWhere for arrays and Buffers (#12577) (a8173fc)
• persistence: preserve select false columns on the in-memory entity after save() (#12501) (324c46c)
• postgres: improve normalizeDatetimeFunction for tstzrange data type (#12182) (bf47c9f)
• query-builder: reject empty where criteria on update and delete operations (#12629) (81b9466)
• query-builder: wrap inner joins under left joins correctly (#11137) (d5f4b9d)
• remove require() calls that break bundlers (#12647) (30f9fc7)
• tree-entity: tree entity schema propagation in internal TreeRepository methods (#12590) (7fb7c2c)

Full Changelog: typeorm/typeorm@0.3.30...0.3.31

Changelog

Sourced from typeorm's changelog.

0.3.31 (2026-07-13)

Bug Fixes

• docs: correct project name in release flow (#12519) (3b9faa3)
• docs: resolve docs workflow issues (c3c09b0)
• docs: resolve docs workflow issues (f7b4b63)
• entity-manager: validate where criteria in increment/decrement (#12692) (a69a8c6)
• migration: escape backslashes and interpolation in generated template literals (b175f9b)
• normalization of FindOptionsWhere for arrays and Buffers (#12577) (a309182)
• persistence: preserve select false columns on the in-memory entity after save() (#12501) (d8e9127)
• query-builder: reject empty where criteria on update and delete operations (#12629) (dfd972b)
• tree-entity: tree entity schema propagation in internal TreeRepository methods (#12590) (e1f93da)

Commits

• 7973203 ci: publish to npm from v0 using the legacy tag
• 92e9276 ci: use npm@11
• 099c23e chore: prepare release 0.3.31 (#12676)
• b175f9b Merge commit from fork
• a69a8c6 fix(entity-manager): validate where criteria in increment/decrement (#12692)
• dfd972b fix(query-builder): reject empty where criteria on update and delete operatio...
• a2d4363 chore: update deps (#12661)
• e1f93da fix(tree-entity): tree entity schema propagation in internal TreeRepository m...
• a309182 fix: normalization of FindOptionsWhere for arrays and Buffers (#12577)
• d8e9127 fix(persistence): preserve select false columns on the in-memory entity after...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	typeorm@​0.3.30 ⏵ 0.3.31		+2	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm typeorm is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/typeorm@0.3.31 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typeorm@0.3.31. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm typeorm is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/typeorm@0.3.31 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typeorm@0.3.31. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/@grpc/grpc-js@1.14.4 → npm/typeorm@0.3.31 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[shocknet-justin]

@cursoragent verify this is a false positive

[cursor]

Verdict: This is a false positive. The Socket "obfuscated code" alert on typeorm@0.3.31 is a heuristic misfire on a legitimate, widely used package — not evidence of malware or a compromised dependency.

What Socket flagged

Socket reports typeorm@0.3.31 as "90% likely obfuscated." That heuristic treats certain compiled or machine-generated JavaScript patterns as obfuscation. It is meant to trigger deeper review, not to serve as a final malware verdict.

Why this is a false positive

1. TypeORM is a known, trusted package

• Official repository: typeorm/typeorm
• Published to the official npm registry (registry.npmjs.org)
• MIT license, millions of weekly downloads
• 0.3.31 matches the official GitHub release (2026-07-13)
• package-lock.json resolves to the expected tarball with a matching integrity hash

2. The code is compiled TypeScript, not malicious obfuscation

Inspecting the installed package shows:

• 1,161 .js files — standard tsc output from the TypeORM build
• Readable identifiers — e.g. EntityManager, FindOptionsUtils, PlainObjectToNewEntityTransformer
• JSDoc comments preserved in the compiled output
• Source maps (.js.map) shipped alongside every file
• No install hooks — no postinstall, preinstall, or install scripts in package.json

Sample from EntityManager.js:

/**
 * Entity manager supposed to work with any entity, automatically find its repository...
 */
class EntityManager {

That is normal compiler output, not javascript-obfuscator-style packing.

3. No suspicious runtime patterns

A scan of the package found no typical malware indicators (eval(), atob(), hex-encoded strings, _0x variable names). The only Function() usage is in ImportUtils.js for dynamic import() — a known, benign pattern for ESM compatibility.

4. The version bump is a routine patch release

Comparing 0.3.30 → 0.3.31 tarballs:

• 3,068 → 3,074 files (only 6 new files)
• New files are InvalidFindOptionsWhereBehavior types — part of the documented bug fix for stricter where validation (#12690)
• The compiled code style is identical between versions

This alert would almost certainly have fired on 0.3.30 as well; it appears on this PR because Socket rescans changed dependencies.

5. Socket's own scores contradict a real threat

Socket's dependency table for this bump shows:

Metric	Score
Vulnerability	100
Quality	100
Maintenance	98
Supply Chain Security	81

Only the obfuscation heuristic fired. If this were a compromised package, you'd expect additional behavioral or reputation signals.

6. Project compatibility confirmed

The project builds successfully with typeorm@0.3.31. TypeORM is used throughout src/services/storage/ for SQLite entity management — standard, expected usage.

Recommendation

Safe to merge this Dependabot PR. The obfuscation alert is noise from Socket's heuristic misclassifying TypeORM's large compiled JavaScript distribution.

If you want to silence the alert on this PR, you can reply on the PR with:

@SocketSecurity ignore npm/typeorm@0.3.31

For a longer-term fix (since this will recur on future TypeORM bumps), consider a socket.yml with issueRules.obfuscatedFile: false — a pattern other projects use for trusted packages that ship minified or compiled builds.