Convert from yarn to npm

[peachbits]

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

• Yes
• No

Dependencies

none

Description

none

---

Note

Low Risk
Changes are limited to package manager, CI scripts, lockfile, and lint config; runtime library code is untouched, though temporarily relaxed ESLint rules reduce guardrails until a follow-up.

Overview
Switches the repo from Yarn to npm for installs, CI, and docs: Travis runs npm run verify, README/CHANGELOG use npm install / npm run *, .yarnrc is removed, and package-lock.json is no longer gitignored (per CHANGELOG: yarn.lock → lockfile, scripts, and Yarn resolutions → npm overrides).

Linting moves to ESLint 9 flat config: .eslintrc.json / .eslintignore are dropped in favor of eslint.config.mjs with eslint-config-standard-kit v1. Several legacy lib/ and flow-typed paths are ignored because the default parser cannot parse them yet, and a large block of style/rules is turned off temporarily so CI passes (follow-up expected).

No application/runtime code changes appear in this diff—only developer workflow, lockfile, dependency overrides, and lint tooling.

^{Reviewed by Cursor Bugbot for commit 8b03935. Bugbot is set up for automated code reviews on this repo. Configure here.}

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	webpack@​5.89.0 ⏵ 5.104.1	-7	+4
	eslint-config-standard-kit@​0.15.1 ⏵ 1.0.0	-1		+1	+3
	@​babel/​runtime@​7.23.1 ⏵ 7.26.10	+1	+2
	elliptic@​6.5.4 ⏵ 6.6.1	+1	+75
	rollup@​2.79.1 ⏵ 2.80.0	-4	+22
	base-x@​4.0.0 ⏵ 4.0.1	+1	+16	+1
	eslint@​7.32.0 ⏵ 9.39.4	-1		+1	+45
	typescript@​4.4.4 ⏵ 5.8.3	+1		-10		+10
	webpack-dev-server@​4.15.2 ⏵ 5.2.4	+1	+4
	mocha@​10.1.0 ⏵ 10.6.0	+1		+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 @typescript-eslint/eslint-plugin is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/eslint-config-standard-kit@1.0.0 → npm/@typescript-eslint/eslint-plugin@8.59.4 ℹ 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/@typescript-eslint/eslint-plugin@8.59.4. 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 es-abstract is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/npm-run-all@4.1.5 → npm/eslint-config-standard-kit@1.0.0 → npm/es-abstract@1.24.2 ℹ 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/es-abstract@1.24.2. 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 eslint-plugin-react is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/eslint-config-standard-kit@1.0.0 → npm/eslint-plugin-react@7.37.5 ℹ 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/eslint-plugin-react@7.37.5. 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 rollup is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/rollup@2.80.0 ℹ 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/rollup@2.80.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		Obfuscated code: npm string.prototype.trimend is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/npm-run-all@4.1.5 → npm/eslint-config-standard-kit@1.0.0 → npm/string.prototype.trimend@1.0.9 ℹ 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/string.prototype.trimend@1.0.9. 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 workerpool is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/mocha@10.6.0 → npm/workerpool@6.5.1 ℹ 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/workerpool@6.5.1. 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		Low adoption: npm @humanfs/types Location: Package overview From: package-lock.json → npm/eslint@9.39.4 → npm/@humanfs/types@0.15.0 ℹ Read more on: This package | This alert | What are unpopular packages? 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: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@humanfs/types@0.15.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		Low adoption: npm node-exports-info Location: Package overview From: package-lock.json → npm/eslint-config-standard-kit@1.0.0 → npm/node-exports-info@1.6.0 ℹ Read more on: This package | This alert | What are unpopular packages? 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: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/node-exports-info@1.6.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.

View full report

[cursor]

🔒 Agentic Security Review
Severity: MEDIUM

The migration removes the prior install-time lifecycle-script safeguard (--ignore-scripts true in .yarnrc) but now instructs contributors to run plain npm install.

Impact: A compromised dependency can execute preinstall/install/postinstall scripts automatically in developer or CI environments, increasing supply-chain command-execution and secret-exfiltration risk.

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ab5348a. Configure here.}

[cursor]

Missing ESLint build ignores

Medium Severity

Removing .eslintignore dropped global excludes for lib/, root types.js / types.mjs / types.js.flow, and android/src/main/assets/, but eslint.config.mjs only ignores a handful of lib/ files. After npm install runs prepare, npm run verify’s eslint . can lint generated build output that was never meant to be checked.

 

^{Reviewed by Cursor Bugbot for commit ab5348a. Configure here.}

[cursor]

Wrong CHANGELOG prefix security

Low Severity

The Unreleased entry uses the fixed: prefix for Socket-recommended transitive dependency version bumps. Those are dependency maintenance changes, not a correction of incorrect behavior in this library’s own code, so the prefix does not match the repo’s semantic CHANGELOG conventions.

 

^{Triggered by learned rule: CHANGELOG entries must use correct semantic prefix}

^{Reviewed by Cursor Bugbot for commit ab5348a. Configure here.}