iframe-proxy

cryptodev-2s · 2026-09-03T20:34:22Z

Bottom of stack #315.

Core formats with Oxfmt, so once this package moves into packages/ its files get reformatted anyway. Doing it here keeps that diff reviewable instead of landing as noise on top of the migrated git history.

lint:misc switches from Prettier to oxfmt --ignore-path .gitignore
Adds .oxfmtrc.json, copied from core
Turns off prettier/prettier and import/order, same as core
Drops prettier-plugin-packagejson, replaced by Oxfmt's sortPackageJson

Prettier itself stays, and moves to core's versions, because @metamask/eslint-config@15 peer requires all three:

Reformatting touches README.md, src/json.ts and src/__fixtures__/bytes.ts. No content changes.

socket-security · 2026-09-03T20:34:44Z

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

Package	Supply Chain Security	Quality	Maintenance
eslint-config-prettier@8.8.0 ⏵ 9.1.2	⁺¹	⁺¹	^-3
oxfmt@0.44.0
eslint-plugin-prettier@4.2.1 ⏵ 5.5.6	⁺¹
prettier@3.9.6

View full report

socket-security · 2026-09-03T20:34:45Z

Caution

MetaMask internal reviewing guidelines:

Do not ignore-all
Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
@SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert (click "▶" to expand/collapse)
Block		Potential security risk (AI signal): npm `oxfmt` is 62.0% likely risky Notes: This code is a dynamic loader with a direct VM-based execution primitive: it resolves specifiers to filesystem targets, reads module source, optionally transpiles it, and executes the result via vm.runInThisContext. While no explicit exfiltration/malware payload is visible in the excerpt, the combination of (1) arbitrary module-source loading, (2) runtime transformation, and (3) in-process VM execution plus optional persistent fsCache makes it inherently high-risk in supply-chain settings if attackers can influence resolution targets or inputs. Review the package’s initialization/entrypoints and any exposure of specifier/alias/transform options to untrusted control to assess exploitability. Confidence: 0.62 Severity: 0.75 From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What are AI-detected potential security risks? 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: An AI system identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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.
Block		System shell access: npm `oxfmt` in module child_process Module: child_process Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is shell access? 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 avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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.
Block		System shell access: npm `tinypool` in module node:child_process Module: node:child_process Location: Package overview From: package.json → `npm/oxfmt@0.44.0` → `npm/tinypool@2.1.0` ℹ Read more on: This package \| This alert \| What is shell access? 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 avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/tinypool@2.1.0`. 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		Potential code anomaly (AI signal): npm `oxfmt` is 66.0% likely to have a medium risk anomaly Notes: No direct malicious actions (network access, credential theft, persistence, or data exfiltration) are visible in this JavaScript wrapper. However, it has a high-impact code-loading capability: `require(process.env.NAPI_RS_NATIVE_LIBRARY_PATH)` can load arbitrary modules/native code if an attacker can influence that environment variable. Additionally, it executes `ldd --version` during musl detection and relies on many platform-specific compiled native artifacts, so the real risk depends heavily on the integrity of the shipped `.node` files and `@oxfmt/binding-` packages. Overall: moderate supply-chain/runtime abuse risk concentrated in environment-controlled dynamic require and native-code execution. Confidence:* 0.66 Severity: 0.56 From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` reads NAPI_RS_NATIVE_LIBRARY_PATH Env Vars: NAPI_RS_NATIVE_LIBRARY_PATH Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` Env Vars: NAPI_RS_ENFORCE_VERSION_CHECK Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` reads NAPI_RS_FORCE_WASI Env Vars: NAPI_RS_FORCE_WASI Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` reads NODE_DEBUG Env Vars: NODE_DEBUG Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` reads npm_package_name Env Vars: npm_package_name Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` reads npm_lifecycle_script Env Vars: npm_lifecycle_script Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` reads TEST_PSEUDOMAP Env Vars: TEST_PSEUDOMAP Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` reads _nodeLRUCacheForceNoSymbol Env Vars: _nodeLRUCacheForceNoSymbol Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` reads FORCE_COLOR Env Vars: FORCE_COLOR Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` reads PRETTIER_DEBUG Env Vars: PRETTIER_DEBUG Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` reads GRACEFUL_FS_PLATFORM Env Vars: GRACEFUL_FS_PLATFORM Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` Env Vars: TEST_GRACEFUL_FS_GLOBAL_PATCH Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` reads NODE_ENV Env Vars: NODE_ENV Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` reads LANG Env Vars: LANG Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` reads JEST_WORKER_ID Env Vars: JEST_WORKER_ID Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Environment variable access: npm `oxfmt` reads DEBUG Env Vars: DEBUG Location: Package overview From: package.json → `npm/oxfmt@0.44.0` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/oxfmt@0.44.0`. 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		Potential code anomaly (AI signal): npm `prettier` is 60.0% likely to have a medium risk anomaly Notes: No direct evidence of embedded malware (no eval/new Function, no credential theft, no obvious backdoor/persistence, no explicit network exfiltration) is visible in this fragment. The dominant security concern is supply-chain/execution risk: the code dynamically imports and executes formatter plugins based on user/config-supplied plugin identifiers and resolution rooted at process.cwd(). Additionally, it can read/write local files (including writing formatted output back to caller-specified paths) and uses predictable temp JSON files that may be susceptible to interference in shared environments. Security posture depends heavily on whether plugin inputs and file paths are trusted/validated and whether dependency/plugin resolution is constrained. Confidence: 0.60 Severity: 0.55 From: package.json → `npm/prettier@3.9.6` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/prettier@3.9.6`. 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

Core formats with Oxfmt, so once this package moves into packages/ its files get reformatted by core's lint:misc regardless. Doing it here keeps that diff in a reviewable commit instead of landing as noise on top of the migrated git history. lint:misc prettier '**/*.json' '**/*.md' ... -> oxfmt --ignore-path .gitignore Adds .oxfmtrc.json copied from core, minus the merged-packages ignore, plus CHANGELOG.md which auto-changelog owns. Turns off prettier/prettier and import/order in .eslintrc.js, the same two rules and the same reason core gives: handled by Oxfmt. Drops prettier-plugin-packagejson, replaced by Oxfmt's sortPackageJson. The Prettier packages themselves stay and move to the versions core uses, because @metamask/eslint-config@15 peer requires all three: prettier ^2.7.1 -> ^3.3.3 eslint-config-prettier ^8.8.0 -> ^9.1.0 eslint-plugin-prettier ^4.2.1 -> ^5.2.1 Prettier also stays in use for `auto-changelog validate --prettier`. Reformatting touches README.md (list whitespace), src/json.ts and src/__fixtures__/bytes.ts. Build, 23 suites / 1993 tests, tsd and lint pass.

cryptodev-2s mentioned this pull request Sep 4, 2026

chore: bump ESLint stack to v15 and migrate to flat config #317

Open

Base automatically changed from migrate/pr2a-align-deps-tsconfig to main September 4, 2026 06:52

cryptodev-2s force-pushed the migrate/pr2b-prettier branch from db2cba6 to 791b881 Compare September 4, 2026 06:52

cryptodev-2s self-assigned this Sep 4, 2026

cryptodev-2s force-pushed the migrate/pr2b-prettier branch from 791b881 to bec22c8 Compare September 4, 2026 07:16

cryptodev-2s changed the title ~~chore: bump Prettier to ^3.3.3 and interop deps~~ chore: replace Prettier formatting with Oxfmt Sep 4, 2026

cryptodev-2s requested a review from Mrtenz September 4, 2026 10:40

Mrtenz approved these changes Sep 4, 2026

View reviewed changes

cryptodev-2s merged commit 49a0ce5 into main Sep 4, 2026
21 of 22 checks passed

cryptodev-2s deleted the migrate/pr2b-prettier branch September 4, 2026 11:00

Dep	From	To
`prettier`	`^2.7.1`	`^3.3.3`
`eslint-config-prettier`	`^8.8.0`	`^9.1.0`
`eslint-plugin-prettier`	`^4.2.1`	`^5.2.1`

Sunbelt Computer Software

PL/B Language Development and Support

Navigation Menu

Uh oh!

Uh oh!

chore: replace Prettier formatting with Oxfmt - #314

chore: replace Prettier formatting with Oxfmt#314
cryptodev-2s merged 1 commit into
mainfrom
migrate/pr2b-prettier

cryptodev-2s commented Sep 3, 2026 •

edited

Loading

Uh oh!

socket-security Bot commented Sep 3, 2026 •

edited

Loading

Uh oh!

socket-security Bot commented Sep 3, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Sunbelt Computer Software

PL/B Language Development and Support

Uh oh!

Uh oh!

Conversation

cryptodev-2s commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security Bot commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security Bot commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

cryptodev-2s commented Sep 3, 2026 •

edited

Loading

socket-security Bot commented Sep 3, 2026 •

edited

Loading

socket-security Bot commented Sep 3, 2026 •

edited

Loading